Skip to Main Content
Forums

Data Science & Machine Learning

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Weird behavior & error messages from ore.make.names (OREbase package)

Christos Iraklis TsatsoulisMar 3 2015 — edited Mar 9 2015

Hi all,

I am getting some weird error messages when trying to use the ore.make.names function from the OREbase package. I will reproduce them here using the simple example from the function help page:

> library(ORCH)

> xnames <- c("col1", "Col.2", "COL_3", "col 4", "col1",

  "L_A_S_T C.O.L.U.M.N abcdefghijklmnopqrstuvwxyz")

> ore.make.names(xnames)

Error in ore.make.names(xnames) : attempt to apply non-function


Accidentally (trying to confirm that other ORE/ORCH functions were working properly), I executed an ore.connect function, after which the ore.make.names indeed became functional:


> ore.connect(type="HIVE")
> ore.make.names(xnames)
[1] "col1" 

[2] "col_2" 

[3] "col_3" 

[4] "col_4" 

[5] "col1_1" 

[6] "l_a_s_t_c_o_l_u_m_n_abcdefghijklmnopqrstuvwxyz"


Nevertheless, if I disconnect, I get again an error message, only a different one this time:


> ore.disconnect()
> ore.make.names(xnames)
Error: '$' is not implemented yet'.ore.QueryEnv' is not implemented yet'makeDBnames' is not implemented yet


Any ideas? Is this possibly a bug?


Let me stress that there is nothing in the ore.make.names documentation to indicate that an ore.connect command is previously required. To my understanding, the function should behave much like the base R make.names function (except if there are different conversion rules for connections to Hive and Oracle database...)


Thanks in advance


Herc


> sessionInfo()  # runs in Oracle BD Lite VM 4.0.1
Oracle Distribution of R version 3.1.1 (--)

Platform: x86_64-unknown-linux-gnu (64-bit)

locale:

[1] C

attached base packages:

[1] stats graphics grDevices utils datasets methods base 

other attached packages:

[1] ORCH_2.4.1 ORCHstats_2.4.1 ORCHcore_2.4.1 OREstats_1.4.1

[5] MASS_7.3-33 OREbase_1.4.1 

loaded via a namespace (and not attached):

[1] tools_3.1.1
This post has been answered by Sherry Lamonica-Oracle on Mar 6 2015
Jump to Answer

Comments

JohnWatson2

It is all in here,

http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf

BPeaslandDBA

From Google Translate: 



What is the end date of the holder 11.2.0.4 ?


Can we keep the standard edition and standard edition licenses one or should we switch to standard edition 2 from 09.16.2016 ?


Finally it is possible to switch to standard edition 2 and stay 11.2.0.4 oracle ?

What is the end date of the holder 11.2.0.4 ?


Answered here: https://blogs.oracle.com/UPGRADE/entry/premier_support_for_oracle_11


Can we keep the standard edition and standard edition licenses one or should we switch to standard edition 2 from 09.16.2016 ?


I can't answer that one. SE2 was recently announced. I know some customers are worried that they won't be able to switch from SE1 to SE2 but I can't say for certain if their fears are valid or not. I don't use SE1 so I don't have first-hand experience.


Finally it is possible to switch to standard edition 2 and stay 11.2.0.4 oracle ?


It won't be. The first SE2 version is 12.1.0.2. There is no 11.2.0.4 SE1.


Hope that helps,

Brian

JohnWatson2

I see I missed one bit of your question: what to do with SE1 licences. Well, nothing! You cannot upgrade your SE1 databases to 12.1.0.2, they must stay at 12.1.0.1 or lower. If you want to go to the current release, you'll have to adjust the licence to SE2 and pay accordingly.

Furthermore, SE1 will no longer be available for purchase after 1 December, so if you want more SE1 licenses, do not hang about.

1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 6 2015
Added on Mar 3 2015
#r-technologies
2 comments
1,330 views