Skip to Main Content

Analytics Software

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!

FDMEE : Open Batch is failling with the periods while ok in FDM Classic...

TipiakJun 27 2014 — edited Jun 27 2014

Hello,

I was using OpenBatch feature in FDM Classic and now I'm trying to use it in FDMEE...

Source = flatfile

Target = Essbase

- In FDM Classic, you don't need to specify the start & end period because FDM is reading the period from the file name.

- In FDMEE, I'm forced to give a start/end period in the command line

     => and if I put for example Start Period = Jan-2014 & End Period = Dec-2014 in my command line, then if I have no file for Mar-2014, FDMEE will through an error because Mar-2014 file not found and will stop the loading at the import process

Maybe I'm doing something wrong?

Thanks,

Comments

John Thorton

4130935 wrote:

Hello

I just did an upgrade from 12.1 to 12.2 using dbua however I realized that compatible parameter is still set 12.1.0.2.0 although it was upgraded to 12.2

Why didnt dbua change this parameter ? Is it because the flashback was on ?

Oracle  did NOT change COMPATIBLE parameter because it assumed that since you explicitly set it (as opposed to taking Oracle default), that you wanted it set to 12.1.0.2 & left it for you to change it. Problem Exists Between Keyboard And Chair.

TK03

Hi John,

Does it mean that any upgrades with dbua, the compatible parameter will always be same ? DBUA will never change that parameter

John Thorton

4130935 wrote:

Hi John,

Does it mean that any upgrades with dbua, the compatible parameter will always be same ? DBUA will never change that parameter

IMO, you are asking the WRONG question.

What does DBUA do when COMPATIBLE is NOT set to any value & the upgrade is performed?

TK03

Compatible is set to 12.1.0.2

After the upgrade with dbua

It is still same.

I thought dbua will change it 12.2.0.1 once the upgrade is finished

John Thorton

4130935 wrote:

Compatible is set to 12.1.0.2

After the upgrade with dbua

It is still same.

I thought dbua will change it 12.2.0.1 once the upgrade is finished

Oracle & reality demonstrated that you thought wrongly.

yoonas

Hi,

You should have spent little more time reading upgrade guide, it has well depth of information.

When to Set the COMPATIBLE Initialization Parameter in Oracle Database

When to Set the COMPATIBLE Initialization Parameter in Oracle Database

Oracle recommends increasing the COMPATIBLE parameter only after you have completed testing the upgraded database.

After the upgrade is complete, you can increase the setting of the COMPATIBLE initialization parameter to the maximum level for Oracle Database 12c. However, after you increase the COMPATIBLE parameter, you cannot subsequently downgrade the database.

Regards,

Yoonas

TK03

1-) does it mean that once i increase the COMPATIBLE parameter, I can never downgrade the database ?

2-) Assume I enabled flashback database before the upgrade and after the upgrade I increased the COMPATIBLE parameter.  Can i still flashback database to before upgrade state ?

dvohra21

To downgrade, first decrease the COMPATIBLE parameter.

John Thorton

dvohra21 wrote:

To downgrade, first decrease the COMPATIBLE parameter.

What happens when a feature that exists in the higher version (& has been used)  does NOT exist in the lower version & attempt a downgrade?

TK03

Hi John,

so once i increase the COMPATIBLE parameter, there is no way to downgrade ?

yoonas

What Is Oracle Database Compatibility?

Downgrading Oracle Database to an Earlier Release

6 Downgrading Oracle Database to an Earlier Release

For supported releases of Oracle Database, you can downgrade a database to the release from which you last upgraded. For example, if you recently upgraded from release 11.2.0.4 to Oracle Database 12c, and you did not change the compatible initialization parameter to 12.1 or higher, then you can downgrade to release 11.2.0.4. If your Oracle Database 12c is release 12.1.0.2, and you did not change the compatible initialization parameter to 12.1.0.2, then you can downgrade to release 12.1.0.1 and so forth.

dvohra21

Seems like not.

"You cannot downgrade a database once you have set the compatible initialization parameter to 12.1.0.2."

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

Post Details

Locked on Jul 25 2014
Added on Jun 27 2014
1 comment
1,191 views