Skip to Main Content
Forums

Java Programming

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!

Version 1.8 RPM Package Name is Incorrect

user9339610Oct 9 2014 — edited Nov 6 2015

I've noticed that RPM package name of JRE and JDK version 1.8u20 is incorrectly named compared to all other RPMs in Linux.

I couldn't figure out why it failed to "update" v1.8u11 to u20, but performing a query on the package reveals the difference in the package name. 

This package will not "update" v1.8v11.

rpm -qp jdk-8u20-linux.x64.rpm

* Results:

jdk1.8.0_20-1.8.0_20-fcs.x86_64

Shouldn't the package name be jdk-1.8.0_20-1.8.0_20-fcs.x86_64 ?

Out of thousands of RPM packages, this is the only one without the "dash" behind the package name and the major version.

Someone on the following thread said it was a "management decision".  Is this true?  Doesn't this break the ease-of-use of RPMs and the RPM standard - whatever that really is?

https://bugs.openjdk.java.net/browse/JDK-8055864

If you want multiple versions of JDK on a system, then use the TAR files and drop them where ever you want.

Will this change in 1.8u21+?

I also heard that Red Hat may start charging an additional fee for their packaged Java repository when they release their latest version of it.  Is this related to changes in Oracle policy?

Not sure if any of this is true or not.  Maybe this is a side affect of the change?! 

Don't you just love policy changes?

Comments

Gianni Ceresa

So the question is This question is Assumed Answered. without any reply. Does it mean you found your own answer?

In this case you maybe don't want to forget the concept of Community forum: you get and you give. You found your answer? Share it to help others having the same issue. If you don't, why would others invest their time in helping you next time?

RAMAKRISHNA K

Hi Gianni,

This was my 1st time using the tool so mistakenly cliked something as i was not aware. Let me know how to revert that option.

Apologies in advance

Gianni Ceresa

Ok, so you still have the question, that's the important piece

As your screenshot doesn't expand "dbo", are you saying that underneath "dbo" you have an existing "ADW12_XX" schema with already a bunch of tables inside?

RAMAKRISHNA K

Hi Gianni,

Yes, dbo have an existing schema "ADW12_XX" with already a bunch of tables. when i am importing the tables or column from existing schema by Oracle Datawarehouse connection pool. the table(ex: ABC_CLASS_TMP) importing to under "ADW12_XX" schema which is newly generated.

Table ABC_CLASS_TMP should be import existing schema under "dbo" but it's not..

Could you please help me explain why this happens.

Thanks in advance..

pastedImage_0.png

Gianni Ceresa

What you see isn't really wrong, and not a big deal.

A Catalog is (based on the doc) :

Physical layer catalogs are optional ways to group different schemas.
A catalog contains all the schemas (metadata) for a physical database object. A schema contains only the metadata information for a particular user or application.

Therefore it isn't a real database object, it's just an artifact. When you import a new table OBIEE add it where it naturally belongs to: a table into a schema right underneath the database object. But once it's imported you can move the table where you want it. You must easily be able to move it in the right location and delete leftovers.

The advantage of the import is mainly to create all the columns etc., so if you have to move the imported object it isn't a big deal versus all the time you spare compared if you had to create everything by hand.

1 - 5

Post Details

Added on Oct 9 2014
#java-8-questions
3 comments
2,856 views