EBS 12.2.0 NLS did not go through successfully

[erman]

strange problems  I think your db is in a unstable state. objects seem partially deployed.. maybe because of the previous patch failure. go to $FND_TOP and try to find a pls file that contains your problematic package.. you can use grep -r for this...

if you find a pls , take the action that you have taken by following the note that I have previously sent.

[Max]

Yes it is. Obviously the problem is that previous patch failed. No, I can't find any *.pls for fix the problem. I think I just need new installation again.

[erman]

also check your patch folder use grep -r in your patch folder .. patch may have a file for recreating this package.. use gre -r packagename *.

I can send you the spec and body of the package from my environments , but there is no guarantee .. I mean you may have other problematic db objects too.

make a new installatin then..
take a backup after the installation. also take another backup before the 12.2.4 upgrade patch when the time comes.

[Max]

Hello Erman. Now during applying NLS errors appears in workers

FNDLOAD APPS/***** 0 Y UPLOAD @XLA:patch/115/import/xlaemseed.lct @OKL:patch/115/import/RU/oklemseed.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE

Calling FNDLOAD function.

Returned from FNDLOAD function.

Log file: /opt/vis13/fs_ne/EBSapps/log/adop/4/apply_20150408_150835/VIS13_db3h-dev/20770978_RU/log/RU_oklemseed_ldt.log
Error calling FNDLOAD function.

And inside this log

Current system time is Wed Apr  8 15:10:30 2015


CURRENT SESSION_ID is : 2426321
CURRENT EDITION_NAME is : ORA$BASE
 
Uploading from the data file /opt/vis13/fs1/EBSapps/appl/okl/12.0.0/patch/115/import/RU/oklemseed.ldt
Altering database NLS_LANGUAGE environment to RUSSIAN
Dumping from LCT/LDT files (/opt/vis13/fs1/EBSapps/appl/xla/12.0.0/patch/115/import/xlaemseed.lct(120.22), /opt/vis13/fs1/EBSapps/appl/okl/12.0.0/patch/115/import/RU/oklemseed.ldt) to staging tables
Dumping LCT file /opt/vis13/fs1/EBSapps/appl/xla/12.0.0/patch/115/import/xlaemseed.lct(120.22) into FND_SEED_STAGE_CONFIG
Dumping LDT file /opt/vis13/fs1/EBSapps/appl/okl/12.0.0/patch/115/import/RU/oklemseed.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (XLA_SUBLEDGERS OKL , XLA_SOURCES S OKL_KHR_ID ) into FND_SEED_STAGE_ENTITY
Uploading from staging tables
  Error loading seed data for XLA_ENTITY_TYPES:  APPLICATION_SHORT_NAME = OKL, ENTITY_CODE = AM_QUOTES,  ORA-01403: данные не найдены
  Error loading seed data for XLA_EVENT_CLASSES:  APPLICATION_SHORT_NAME = OKL, ENTITY_CODE = AM_QUOTES, EVENT_CLASS_CODE = ESTIMATED_BILLING,  ORA-01403: данные не найдены
  Error loading seed data for XLA_EVENT_TYPES:  APPLICATION_SHORT_NAME = OKL, ENTITY_CODE = AM_QUOTES, EVENT_CLASS_CODE = ESTIMATED_BILLING, EVENT_TYPE_CODE = ESTIMATED_BILLING_ALL,  ORA-01403: данные не найдены
  Error loading seed data for XLA_EVENT_TYPES:  APPLICATION_SHORT_NAME = OKL, ENTITY_CODE = AM_QUOTES, EVENT_CLASS_CODE = ESTIMATED_BILLING, EVENT_TYPE_CODE = ESTIMATED_BILLING_CREATE,  ORA-01403: данные не найдены

[ErmanArslansOracleBlog]

it seems like it is a data issue.
The patch may be wrong, or a needed data is not in place. I mean ; probably before loading this data, another data should be loaded,should be in place and because this prepreq data is not loaded, you get "no data found errors"

What is the number of the patch in which you encounter this error?

[Max]

This is Russian NLS p17919161_RU.

 number 5 Perform NLS-related Step (conditional) from Doc ID 1617458.1

[Max]

Now the problem is

Start time for file is: Wed Apr 08 2015 19:29:09

Invoking Utility XLIFFLoader ...
Class: oracle.apps.xdo.oa.util.XLIFFLoader
Method: processXLIFF
Arguments: UPLOAD -DB_USERNAME &un_apps -DB_PASSWORD &pw_apps -JDBC_CONNECTION &jdbc_db_addr -APPS_SHORT_NAME PA -TEMPLATE_CODE PAXRWPJS_XML -FILE_NAME &fullpath:pa:patch/115/publisher/templates/RU:PAXRWPJS_XML.xlf
**** Reseting package states in the current session ****
TimeStamp : [Wed Apr 08 20:29:09 MSK 2015]
==========================================================
==========================================================
Done calling the utility function. Return Code = [1] TimeStamp = [Wed Apr 08 20:29:09 MSK 2015]

AD Worker error:
The utility XLIFFLoader returned error for the above task.

AD Worker error:
The above program failed.  See the error messages listed
above, if any, or see the log and output files for the program.

Time when worker failed: Wed Apr 08 2015 19:29:09
Updating task with status 1

[ErmanArslansOracleBlog]

check the document 1995999.1.
it is similar to your problem, but the objects are different. it seems you are hitting a bug.. check your failing lct and check your db objects accordingly.also maybe the ldt is buggy..

If you cant find anything useful and if you did everything properly, open an SR. it will probably identified as a bug and they will send you a patch for it.

I checked the support and saw that related issues have been solved by applying patches sent by oracle support.

8 Nis 2015 19:18 tarihinde "Max [via Erman Arslan's Oracle Forum]" <[hidden email]> yazdı:

This is Russian NLS p17919161_RU.

 number 5 Perform NLS-related Step (conditional) from Doc ID 1617458.1

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EBS-12-2-0-NLS-did-not-go-through-successfully-tp216p279.html

To start a new topic under EBS 12.2, email [hidden email]
To unsubscribe from Erman Arslan's Oracle Forum, click here.
NAML

[ErmanArslansOracleBlog]

Is the problem changed? You wrote "now the problem is.."
For the xliffloader problem, you can try to running xliffloader manually.
But you have to run it with the arguments reported in the error.


Following is an example for 12.2:
Read this one: http://ermanarslan.blogspot.com.tr/2014/05/ebs-122-emea-localizations.html
A manual run of xliffloader is;

adjava -mx512m -nojit oracle.apps.xdo.oa.util.XLIFFLoader -DB_USERNAME apps -DB_PASSWORD apps -JDBC_CONNECTION erptest:1521:TEST -APPS_SHOT_NAME IBY -TEMPLATE_CODE IBYD_TR_APSBISTOTSN  -FILE_NAME CLEDE_TR_APSBISTSN.xlf

Try it in your EBS 12.2 . Ofcourse change te argument accordingly.. The arguments are reported in the error message.

If you success by manually running it, then use adctrl and skip the workers job, and continue patching..
Hands-on analysis required if you need more on this, and without hands-on, it will be a time consuming..

anyways, if you cant proceed with xliff and also getting ldt errors no matter what  ; then as I mentioned in my previous update, open a SR, and request a patch for your ldt errors.

[ErmanArslansOracleBlog]

Yes, your xliffloader problem is also a recorded bug.
Bug 20711438 : PATCH17919161 NLS PATCH FAILED ON XLIFFLOADER ON PAXRWPJS_XML TEMPLATE

Open an SR by referencing the bug "Bug 20711438",also state your language is Russian.

[ErmanArslansOracleBlog]

There are 2 bugs actually.. quote a reference for both of them..
Bug 19864703 : errors while applying NLS to fresh R12.2.0 upgraded to R12.2.4

[Max]

Hi. Something strange happening. Since last error I've just replace whole installation. I mean delete old installation and untar new installation from 12.2.4 tar without NLS. So I've taken NLS patch V36823-01 from edelivery.oracle.com just for test. And now I have different error.

adop phase=apply patches=10124646_RU:u10124646.drv hotpatch=yes restart=no wait_on_failed_job=yes workers=5

log file is: /opt/vis13/fs_ne/EBSapps/log/adop/3/apply_20150410_164848/VIS13_db3h-dev/10124646_RU/log/u10124646.log

and error is:

Time is: Fri Apr 10 2015 17:01:16

   FAILED: file cua12alu.ldt on worker  4 for product cua username APPS.

Time is: Fri Apr 10 2015 17:01:16

 Deferred: file cua12alu.ldt on worker  4 for product cua username APPS.

Time is: Fri Apr 10 2015 17:01:16
               (Deferment number 2 for this job)
 Assigned: file fa12alu.ldt  on worker  4 for product fa  username APPS.

Time is: Fri Apr 10 2015 17:01:16

   FAILED: file zxcfctbc.ldt on worker  1 for product zx  username APPS.
...
....
......
....
......

ATTENTION: All workers either have failed or are waiting:

           FAILED: file arirulob.ldt on worker  1.
           FAILED: file cua12alu.ldt on worker  2.
           FAILED: file zxcfctbc.ldt on worker  3.
           FAILED: file fa12alu.ldt  on worker  4.
           FAILED: file falookupjp.ldt on worker  5.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Current time is: Fri Apr 10 2015 17:01:19


So lets see what happened in worker 4

less /opt/vis13/fs_ne/EBSapps/log/adop/3/apply_20150410_164848/VIS13_db3h-dev/10124646_RU/log/adwork004.log

Loading data using  FNDLOAD function.
**** Reseting package states in the current session ****

FNDLOAD APPS/***** 0 Y UPLOAD @OFA:patch/115/import/falku2.lct @CUA:patch/115/import/RU/cua12alu.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE

Calling FNDLOAD function.

Returned from FNDLOAD function.

Log file: /opt/vis13/fs_ne/EBSapps/log/adop/3/apply_20150410_164848/VIS13_db3h-dev/10124646_RU/log/RU_cua12alu_ldt.log
Error calling FNDLOAD function.


Time when worker failed: Fri Apr 10 2015 17:01:16


Time when worker started job: Fri Apr 10 2015 17:01:16

Loading data using  FNDLOAD function.
**** Reseting package states in the current session ****

FNDLOAD APPS/***** 0 Y UPLOAD @OFA:patch/115/import/falku2.lct @OFA:patch/115/import/RU/fa12alu.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE

Calling FNDLOAD function.

Returned from FNDLOAD function.

Log file: /opt/vis13/fs_ne/EBSapps/log/adop/3/apply_20150410_164848/VIS13_db3h-dev/10124646_RU/log/RU_fa12alu_ldt.log
Error calling FNDLOAD function.


But if I execute this FNDLOAD manually all is ok!

$ FNDLOAD APPS/APPS 0 Y UPLOAD @OFA:patch/115/import/falku2.lct @CUA:patch/115/import/RU/cua12alu.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
Log filename : L7457269.log


Report filename : O7457269.out


And no errors in the log file.

+---------------------------------------------------------------------------+
Application Object Library: Version : 12.2

Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.

FNDLOAD: Generic Loader
+---------------------------------------------------------------------------+

Current system time is 10-APR-2015 17:10:10

+---------------------------------------------------------------------------+

Uploading from the data file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt
Altering database NLS_LANGUAGE environment to RUSSIAN
Dump from LCT/LDT files (/opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1), /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt) to stage tables
Dump LCT file /opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1) into FND_SEED_STAGE_CONFIG
Dump LDT file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (FA_LOOKUP_TYPES IFA_HR_EVENT_CODE , FA_LOOKUPS RETIREMENT ) into FND_SEED_STAGE_ENTITY
Upload from stage tables

+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 10-APR-2015 17:10:10

+---------------------------------------------------------------------------+

[ErmanArslansOracleBlog]

Your workers are waiting for the failed jobs right?
So normally, if you can execute this failed jobs manually, and if you success to get them work, then you can skip the failing jobs and continue patching.

But you should see the logs of the failed actions too.. According to this you need to make a decision

In this case not only the workers logs..

so,

1)
What is written in the failed ldt logs?
For example this one: /opt/vis13/fs_ne/EBSapps/log/adop/3/apply_20150410_164848/VIS13_db3h-dev/10124646_RU/log/RU_cua12alu_ldt.log

2)
And did you check that you may be using the run edition and the patch may be using the patch edition environment? I mean you execute and success in the run edition, but the patch may be doing these in the patch edition? Did you check that?

[Max]

Hi. Yes workers are waiting this failed jobs. I can execute FNDLOAD stuff manually and skip this failed jobs, but some time later workers fails again in the same point.

1. In this log no errors.

Current system time is Fri Apr 10 16:50:24 2015


CURRENT SESSION_ID is : 2436019
CURRENT EDITION_NAME is : ORA$BASE
 
Uploading from the data file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt
Altering database NLS_LANGUAGE environment to RUSSIAN
Dumping from LCT/LDT files (/opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1), /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt) to staging tables
Dumping LCT file /opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1) into FND_SEED_STAGE_CONFIG
Dumping LDT file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (FA_LOOKUP_TYPES IFA_HR_EVENT_CODE , FA_LOOKUPS RETIREMENT ) into FND_SEED_STAGE_ENTITY
Uploading from staging tables


Concurrent request completed
Current system time is Fri Apr 10 16:50:24 2015




Current system time is Fri Apr 10 17:01:16 2015


CURRENT SESSION_ID is : 2436021
CURRENT EDITION_NAME is : ORA$BASE
 
Uploading from the data file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt
Altering database NLS_LANGUAGE environment to RUSSIAN
Dumping from LCT/LDT files (/opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1), /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt) to staging tables
Dumping LCT file /opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1) into FND_SEED_STAGE_CONFIG
Dumping LDT file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (FA_LOOKUP_TYPES IFA_HR_EVENT_CODE , FA_LOOKUPS RETIREMENT ) into FND_SEED_STAGE_ENTITY
Uploading from staging tables


Concurrent request completed
Current system time is Fri Apr 10 17:01:16 2015




Current system time is Fri Apr 10 17:01:19 2015


CURRENT SESSION_ID is : 2436019
CURRENT EDITION_NAME is : ORA$BASE
 
Uploading from the data file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt
Altering database NLS_LANGUAGE environment to RUSSIAN
Dumping from LCT/LDT files (/opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1), /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt) to staging tables
Dumping LCT file /opt/vis13/fs1/EBSapps/appl/fa/12.0.0/patch/115/import/falku2.lct(120.1) into FND_SEED_STAGE_CONFIG
Dumping LDT file /opt/vis13/fs1/EBSapps/appl/cua/12.0.0/patch/115/import/RU/cua12alu.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (FA_LOOKUP_TYPES IFA_HR_EVENT_CODE , FA_LOOKUPS RETIREMENT ) into FND_SEED_STAGE_ENTITY
Uploading from staging tables


Concurrent request completed
Current system time is Fri Apr 10 17:01:19 2015


2. I don't get you what you mean. I execute ". /opt/vis13/EBSapps.env run" to initialize environment.

[ErmanArslansOracleBlog]

How did you skip the job?
Please list the actions you gave taken to make the adworkers to the failed jobs.

[Max]

Hi. All is ok after I had done steps from this document: Doc ID 1531121.1

[ErmanArslansOracleBlog]

Hi.
Good.
You dont have any custom code.
So you have take the appropriate actions stated in the report file adzdpsum.txt which was generated by The ADZDPSUM.sql SQL script. Right?

Which actions was listed in the report? Just wondering.

[Max]

I've executed this steps from the dcument

Step 1

---------
1. Run the file $AD_TOP/patch/115/sql/adzddtsfix.sql (Following the usage instructions provided in it).
2. Run the $AD_TOP/sql/ADZDDBCC.sql script to identify whether the data dictionary corruption is still present.

And had did one extra step through adadmin, "Maintain multi-lingual tables" despite that I already have done this step before.

[Muthu]

Is this issue got fixed?
I'm getting same error.

[ErmanArslansOracleBlog]

Hi Muthu,

1531121.1 should solve this, as mentioned in above comments.