EBS 12.2.0 NLS did not go through successfully

classic Classic list List threaded Threaded
60 messages Options
123
Max
Reply | Threaded
Open this post in threaded view
|

EBS 12.2.0 NLS did not go through successfully

Max
Hello Erman, I have a problem with NLS installation. Could you please help me.

So, after rapid install of EBS 12.2.0 VISION I've tried to apply Russian NLS.

1. I've executed adadmin and choose this items (4. Maintain Applications Database Entities menu and 3. Maintain multi-lingual tables)
2. After that I've tried to apply patch (adop phase=prepare,apply,finalize,cutover,cleanup patches=10124646_RU:u10124646.drv)

But adop has a error

Enabling EBS_LOGON trigger
Error while execution /opt/vis5/fs2/EBSapps/10.1.2/bin/sqlplus -s APPS/apps @ /opt/vis5/fs2/inst/apps/VIS5_db3h-dev/appltmp/alter_ebs_logon_trigger.sql > /opt/vis5/fs2/inst/apps/VIS5_db3h-dev/appltmp/ebs_logon_proc_res.log 2>&1
*******FATAL ERROR*******
PROGRAM : (/opt/vis5/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)
TIME    : Fri Mar 20 12:06:57 2015
FUNCTION: main::runFSCloneApply [ Level 1 ]
ERRORMSG: /opt/vis5/fs1/EBSapps/comn/clone/bin/adclone.pl did not go through successfully.

              [ERROR]     Error occurred while executing <perl /opt/vis5/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/opt/vis5/fs1/inst/apps/VIS5_db3h-dev/appl/admin/VIS5_db3h-dev.xml -patchcontextfile=/opt/vis5/fs2/inst/apps/VIS5_db3h-dev/appl/admin/VIS5_db3h-dev.xml -promptmsg=hide -console=off -mode=create -sessionid=3 -timestamp=20150320_114059 -outdir=/opt/vis5/fs_ne/EBSapps/log/adop/3/prepare_20150320_114059/VIS5_db3h-dev>
              [ERROR]     Error occurred while CLONE PATCH FS with RUN FS using command: <perl /opt/vis5/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/opt/vis5/fs1/inst/apps/VIS5_db3h-dev/appl/admin/VIS5_db3h-dev.xml -patchcontextfile=/opt/vis5/fs2/inst/apps/VIS5_db3h-dev/appl/admin/VIS5_db3h-dev.xml -promptmsg=hide -console=off -mode=create -sessionid=3 -timestamp=20150320_114059 -outdir=/opt/vis5/fs_ne/EBSapps/log/adop/3/prepare_20150320_114059/VIS5_db3h-dev>.
              [STATEMENT] fs_clone phase completed with errors/warnings. Please check logfiles
              [ERROR]     Error while runPendingClone sub-routine is called
              [STATEMENT] [START 2015/03/20 12:06:59] Check and Stop Patch Admin Server
                [STATEMENT] There is a pending clone session for /opt/vis5/fs2.
                [STATEMENT] Skipping Check and Stop Patch Admin Server Step.
              [STATEMENT] [END   2015/03/20 12:07:02] Check and Stop Patch Admin Server
              [STATEMENT] Prepare phase completed with errors/warnings. Please check logfiles
              [STATEMENT] PREPARE Phase END TIME: 20-03-2015 12:07:06
              [STATEMENT] [START 2015/03/20 12:07:07] Unlocking sessions table
              [STATEMENT] [END   2015/03/20 12:07:08] Unlocking sessions table
              [STATEMENT] Log file: /opt/vis5/fs_ne/EBSapps/log/adop/3/adop_20150320_114059.log

adop exiting with status = 1 (Fail)

But /opt/vis5/fs2/EBSapps/10.1.2/bin/sqlplus isn't exists, because all directories in /opt/vis5/EBSapps moved to obsolete directories. That's  why adop failed. But I can't figure out how I can fix it?

Can you help me?
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
Please send me the following;

1)/opt/vis5/fs_ne/EBSapps/log/adop/3/adop_20150320_114059.log
2) adop -status -detail
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
$ adop -status -detail

Enter the APPS username: apps
Enter the APPS password:
declare
*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at line 13



adop exiting with status = 1 (Fail)
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
Is your syntax right?

"adop -status -detail"

There are 2 arguments with "-"  in front of them.
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
Also, try
adop -status     (without -detail)
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
Also note that using 12.2.0 is not recommended.
After installing 12.2.0, it is better to directly upgrade it to the latest release(currently 12.2.4) immediately.
NLS patches and localizations should be applied later.. I mean; it is better to apply the NLS patches after your system will be upgraded to the recommended patchset.

So, I suggest you to install VISION
Upgrade it to 12.2.4, then request a translation syncronziation patch for Russian and apply it to the 12.2.4.

But still if you want an investigation about your current problem, we can continue..
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
In reply to this post by ErmanArslansOracleBlog
$ adop -status

Enter the APPS username: apps
Enter the APPS password:


Current Patching Session ID: 3

Node Name Node Type Phase    Status    Started   Finished  Elapsed
--------------- --------------- ----------- --------------- ------------------------------ ------------------------------ ------------
db3h-dev master PREPARE     COMPLETED    23-MAR-15 04:49:32 +03:00   23-MAR-15 05:06:44 +03:00  0:17:12
                                APPLY    FAILED    23-MAR-15 05:07:14 +03:00   23-MAR-15 05:13:49 +03:00  0:06:35
                                CUTOVER     NOT STARTED
                                CLEANUP     NOT STARTED




File System Synchronization Used in this Patching Cycle: None

For more information, see the full ADOP Status Report.
Generating full ADOP Status Report at location: /opt/vis8/fs_ne/EBSapps/log/status_20150323_171431/adzdshowstatus.out
Please wait...
Done...!
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
Please send me the following log file as I already requested in my first reply:
/opt/vis5/fs_ne/EBSapps/log/adop/3/adop_20150320_114059.log


Also send me the following output file:
/opt/vis8/fs_ne/EBSapps/log/status_20150323_171431/adzdshowstatus.out
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
In reply to this post by Max
By the way, in the end I need EBS 12.2.4. I just thought that I need install 12.2.0+NLS and after that upgrade. I can download Russian NLS from e-delivery. (Oracle E-Business Suite NLS Release 12.2.4 - Russian V46216-01). Is it correct NLS or not?
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
No, following should be your action plan.

Install 12.2.0.
Upgrade it to 12.2.4
After the upgrade once you finish all the patches ->
Request a translation syncronization patch for Russion  and apply that for russian translation..
R11i / R12 : Requesting Translation Synchronization Patches (Doc ID 252422.1)

"At the end, Your 12.2.4 system will include russian."
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
In reply to this post by ErmanArslansOracleBlog
So, I suggest that, I'll install new VISION 12.2.0 in the new home upgrade it to 12.2.4 and will try to apply NLS. Ok?
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
In reply to this post by ErmanArslansOracleBlog
12.2.0 is something that it s not event supported.. It does not even include dual filesystem aware env file..

I dont want to say that your problem is caused by being on 12.2.0, I dont have the logs and necessary information, but ;
Normally , in a EBS 12.2 installation ; you should immediately upgrade 12.2.0 to 12.2.4.. If you dont do that and if you play with it; you can end up with these abnormal situations..

For you current problem, please send me the logs I have requested.
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
In reply to this post by Max
Ok.
Install 12.2.0 upgrade it to 12.2.4 and then apply NLS Russion patch for 12.2.4 (you can request translation sync patch for this)

Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
In reply to this post by ErmanArslansOracleBlog
I think we can forget about my current situation. I just make new installation and upgrade it to 12.2.4
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
In reply to this post by ErmanArslansOracleBlog
By the way, why I can't use this patch? (Oracle E-Business Suite NLS Release 12.2.4 - Russian V46216-01) from e-delivery.
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

ErmanArslansOracleBlog
Administrator
I suggest you to upgrade 12.2.4 (without NLS) then add NLS language using note "Oracle E-Business Suite Maintenance Guide", then follow to synronize your translations (11i / R12 : Requesting Translation Synchronization Patches (Doc ID 252422.1))

because, there are some patches which you will apply before the 12.2.4 upgrade and some of those patches are nls versions too.. So by applying only the EBS 12.2.4 NLS patch, you are at risk .. You may be missing NLS translatios of those patches..

So it s better to go with the above action plan.
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
Hello Erman. So after applied EBS patch 12.2.4 I tried to execute this steps. prepare, apply, finalize, cutover, cleanup. But step fs_clone is failed.

$ adop -status

Enter the APPS password:




Current Patching Session ID: 3

Node Name Node Type Phase Status Started       Finished      Elapsed
--------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------
db3h-dev master FS_CLONE FAILED 24-MAR-15 01:48:59 +03:00
                                PREPARE NOT APPLICABLE
                                APPLY NOT APPLICABLE
                                CUTOVER NOT APPLICABLE
                                CLEANUP NOT APPLICABLE




File System Synchronization Used in this Patching Cycle: Full



Note:  fs_clone is required at db3h-dev node before starting the next online patching cycle.


For more information, run ADOP Status Report by using -detail option
Generating ADOP Status Report at location: /opt/vis11/fs_ne/EBSapps/log/status_20150324_140239/adzdshowstatus.out
Please wait...
Done...!

adop exiting with status = 0 (Success)
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
Log file located at /opt/vis11/fs2/inst/apps/VIS11_db3h-dev/admin/log/clone/FSCloneApplyAppsTier_03241459.log
contextfile=/opt/vis11/fs1/inst/apps/VIS11_db3h-dev/appl/admin/VIS11_db3h-dev.xml

Enabling EBS_LOGON trigger

ERROR while running FSCloneApply...
Tue Mar 24 13:59:08 2015
*******FATAL ERROR*******
PROGRAM : (/opt/vis11/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)
TIME    : Tue Mar 24 13:59:08 2015
FUNCTION: main::runFSCloneApply [ Level 1 ]
ERRORMSG: /opt/vis11/fs2/EBSapps/comn/adopclone_db3h-dev/bin/adclone.pl did not go through successfully.

          [UNEXPECTED]Error occurred while executing "perl /opt/vis11/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/opt/vis11/fs2/inst/apps/VIS11_db3h-dev/appl/admin/VIS11_db3h-dev.xml -patchcontextfile=/opt/vis11/fs1/inst/apps/VIS11_db3h-dev/appl/admin/VIS11_db3h-dev.xml -promptmsg=hide -console=off -mode=create -sessionid=3 -timestamp=20150324_134828 -outdir=/opt/vis11/fs_ne/EBSapps/log/adop/3/fs_clone_20150324_134828/VIS11_db3h-dev"
          [UNEXPECTED]Error occurred while CLONE Patch File System from Run File System using command: "perl /opt/vis11/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/opt/vis11/fs2/inst/apps/VIS11_db3h-dev/appl/admin/VIS11_db3h-dev.xml -patchcontextfile=/opt/vis11/fs1/inst/apps/VIS11_db3h-dev/appl/admin/VIS11_db3h-dev.xml -promptmsg=hide -console=off -mode=create -sessionid=3 -timestamp=20150324_134828 -outdir=/opt/vis11/fs_ne/EBSapps/log/adop/3/fs_clone_20150324_134828/VIS11_db3h-dev".
          [EVENT]     Calling task: "Releasing ports on db3h-dev"; script: "/opt/vis11/fs2/inst/apps/VIS11_db3h-dev/admin/install/txkCloneAcquirePort.pl"; args: " -option=close -server=db3h-dev.oebs.yandex.net -ports=5576,7021,7621,7421,7221,7821,6120,6220 -log=/opt/vis11/fs_ne/EBSapps/log/adop/3/fs_clone_20150324_134828/VIS11_db3h-dev/txkCloneAcquirePort.log"
          [EVENT]     [START 2015/03/24 13:59:09] Releasing ports on db3h-dev
            [EVENT]     Calling: /opt/vis11/fs2/inst/apps/VIS11_db3h-dev/admin/install/txkCloneAcquirePort.pl
          [EVENT]     [END   2015/03/24 13:59:09] Releasing ports on db3h-dev
            [ERROR]     Environment file: /opt/vis11/fs1/EBSapps/appl/APPSVIS11_db3h-dev.env does not exists

            Log file: /opt/vis11/fs_ne/EBSapps/log/adop/3/adop_20150324_134828.log


[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.


adop exiting with status = 2 (Fail)
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
Heee is a link for a log: https://yadi.sk/i/yaOvyaZOfUmGh
Max
Reply | Threaded
Open this post in threaded view
|

Re: EBS 12.2.0 NLS did not go through successfully

Max
Link isn't work if you just click on it. You need to copy and paste to address line.
123