OBIA Data Load by DAC causing Account Lock

I was implementing Oracle Business Intelligence Application 7.9.6. on one client site in Middle East . Everything was fine when my data warehouse was on Oracle Database 10.1.X but on DBA suggestion they changed it to 10.2.0.1.0 . once they changed Database version. it was disaster for me whenever i ran the task from DAC it was showing me Account is Locked…..duhhhhh.

Now DBA was no taking the responsibility at all, by saying this it’s some issue with DAC or TASK. but case was not that at all but i was not able to prove it

After some research i got to know in Oracle 10.2 they setup the default option for “FAILED_LOGIN_ATTEMPTS” as 10 so after 10 unsuccessful attempts DAC is Locking user Name i just used following SQL Statement to rectify this issue

Alter Profile “DEFAULT” LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

Julian to Gregorian Calender Switch impact on Oracle

Do you see something abnormal in following image?

Yes …….what’s this ……?

And same thing you will see on some other ERP solutions / software once you select September 1752.

Answer

The calendar snippet shows that there are no days between October 4 and October 15. This discontinuity is called the “cutover”.

What is Cutover

“This is a hybrid Julian/Gregorian calendar with a cutover on October 4/15 1582.” Any dates before a cutover are Julian, any dates during a cutover are nonexistent, and any dates after a cutover are Gregorian.

Mass Feature Available in Oracle Purchasing R12

Click Link To Download