Oracle World: 10/01/2011

Thursday, October 27, 2011

Wait for a undo record Wait for stopper event to be increased

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Sometimes Parallel Rollback of Large Transaction may become very slow. After killing a large running transaction (either by killing the shadow process or aborting the database) then database seems to hang, or SMON and parallel query servers taking all the available CPU.

In fast-start parallel rollback, the background process SMON acts as a coordinator and rolls back a set of transactions in parallel using multiple server processes.

Fast start parallel rollback is mainly useful when a system has transactions that run a long time before a commit, especially parallel Inserts, Updates, Deletes operations. When SMON discovers that the amount of recovery work is above a certain threshold, it automatically begins parallel rollback by dispersing the work among several parallel processes.

There are cases where parallel transaction recovery is not as fast as serial transaction recovery, because the PQ slaves are interfering with each other. It looks like the changes made by this transaction cannot be recovered in parallel without causing a performance problem. The parallel rollback slave processes are most likely contending for the same resource, which results in even worse rollback performance compared to a serial rollback.

Solution
======

To disable the parallel rollback by setting the following parameter
fast_start_parallel_rollback = false

Refer to Oracle Note ID 464246.1

Get Oracle Certifications for all Exams
Free Online Exams.com

High Redo Log Buffer Wait

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Your instance has spent much of its In Oracle time waiting for the Redo Log.

High Redo Log Buffer Wait findings

	Description
What to do next	Perform one of the following options: n Examine the related Oracle events (lower area), Redo Activity (upper area), to determine the problem type in the Statistics workspace. n Examine high Redo Log Buffer Wait statements in the Activity workspace.
Advice	Use any one of the typical problem scenarios described below. n If the log buffer size is too small, this usually results in long waits for the Log Buffer Space event. Consider increasing the Log_buffer parameter. n If the log buffer size is too big, this usually results in a low number of user commits, high redo wastage statistics, and long waits for the Log File Sync event. Consider decreasing the Log_buffer parameter and/or the hidden LOG_I/O_SIZE parameter. n If there are too many commits, this usually results in long waits for the Log File Sync event and the number of user commits is very high. Consider changing the application flow and logic (by decreasing the commit frequency or using bulk commits [resulting in larger transactions]). n If the LGWR is too slow, check whether Log File Sync is still the dominant event. This may be due to high values for Log File Parallel Write, or because there are not many commits. This may mean that the LGWR is underperforming. Consider moving the log file to a faster, dedicated device. Whenever the Log Buffer Space and Log File Sync events occur together, consider changing the hidden LOG_I/O_SIZE parameter.

Get Oracle Certifications for all Exams
Free Online Exams.com

High RAC/OPS Wait --

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Your instance has spent much of its In Oracle time waiting for RAC or OPS.

High RAC/OPS Wait findings

	Description
What to do next	Perform one of the following options: n Examine the Oracle events that are grouped in the Oracle RAC/OPS Wait. Determine the dominant Oracle event and follow the tuning scenario set by this event in the Statistics workspace. n Examine Load balancing between RAC instances in the Activity workspace. n Examine Heavy objects suffering from RAC Waits in the Activity workspace.
Advice	There are two typical scenarios relevant to RAC Waits. Launch to the Dashboard RAC Database view. This view compares the selected instance with other instances in the same database. From the RAC Database view, examine each of the following issues: n If there is a balancing instances issue, launch to the Activity workspace and identify the root cause for this unbalanced issue. n If there is a RAC Wait event, compare them to other events in the database in the Statistics workspace. n If there are Objects suffering from RAC Waits, launch to the Activity workspace and identify their use across Database instances.

Get Oracle Certifications for all Exams
Free Online Exams.com

ORA-00600: internal error code, arguments: [17059], [0x4633429D8]

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description: Database Crashes

Symptoms:

Database hangs frequently, Database Alert Log file shows "ORA-00600: internal error code, arguments: [17059], [0x4633429D8]"

Many trace files generated causing shortage on storage.

Alert Log file shows:

Mon Jan 18 08:02:21 2010
Errors in file /orasys/ipay/bdump/ipay_j000_12065.trc:
ORA-12012: error on auto execute of job 263
ORA-04030: out of process memory when trying to allocate 127512 bytes (QERGH hash-agg,kllcqas:kllsltba)
ORA-06512: at "WTR.TRANSFER_INTERNET_WEB_PAYMENTS", line 17
ORA-06512: at line 1
Mon Jan 18 08:03:32 2010
Errors in file /orasys/ipay/bdump/ipay_j000_12065.trc:
ORA-12012: error on auto execute of job 1
ORA-04030: out of process memory when trying to allocate bytes (,)
ORA-06512: at "SYSMAN.EMD_MAINTENANCE", line 947
ORA-06512: at line 1
Mon Jan 18 08:03:33 2010
Errors in file /orasys/ipay/bdump/ipay_j000_12065.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-04030: out of process memory when trying to allocate 72 bytes (kxs-heap-d,allocator state)
ORA-12012: error on auto execute of job 1
ORA-04030: out of process memory when trying to allocate bytes (,)
ORA-06512: at "SYSMAN.EMD_MAINTENANCE", line 947
ORA-06512: at line 1

Trace files shows :

Errors in file /orasys/ipay/udump/ipay_ora_4868.trc:
ORA-07445: exception encountered: core dump [kksParseChildCursor()+1180] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFF7FFF2E00] [] []
and
Errors in file /orasys/ipay/bdump/ipay_psp0_6679.trc:
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301: OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3

System Error Log shows:

Jan 19 05:58:29 Gateway2 last message repeated 22 times
Jan 19 06:09:59 Gateway2 ufs: [ID 845546 kern.notice] NOTICE: alloc: /orasys: file system full
Jan 19 06:14:45 Gateway2 last message repeated 2 times
Jan 19 06:15:59 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 5420 (oracle)
Jan 19 06:16:00 Gateway2 last message repeated 1 time
Jan 19 06:16:01 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 4363 (oracle)
Jan 19 06:16:01 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 5420 (oracle)
Jan 19 06:16:02 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 4363 (oracle)
Jan 19 06:16:02 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 5420 (oracle)
Jan 19 06:16:02 Gateway2 ufs: [ID 845546 kern.notice] NOTICE: alloc: /orasys: file system full
Jan 19 06:16:03 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 4363 (oracle)
Jan 19 06:16:06 Gateway2 last message repeated 2 times
Jan 19 06:16:07 Gateway2 ufs: [ID 845546 kern.notice] NOTICE: alloc: /orasys: file system full
Jan 19 06:17:41 Gateway2 last message repeated 1 time
Jan 19 06:24:42 Gateway2 ufs: [ID 845546 kern.notice] NOTICE: alloc: /orasys: file system full
Jan 19 06:26:15 Gateway2 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 5486 (oracle)
Jan 19 06:26:18 Gateway2 last message repeated 3 times

Solution:

1. From the error log, it is clear that there is no swap space, thats the reason for getting the error. involve your system administrators to resolve this problem

2. set the stack size to unlimited

3. Apply Interim patch 5705795

Get Oracle Certifications for all Exams
Free Online Exams.com

Oracle Forms&Reports Cloning "Reports Configuration failed"

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description:

Oracle Forms&Reports 10.1.2.0.1 Cloning failed "Reports Configuration failed"

Symptoms:

Cloning log file shows the below:

[Tue Dec 29 12:57:50 2009 INFO] Container: reports

[Tue Dec 29 12:57:51 2009 INFO] Error creating the reports app entity

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.repository.directory.DirectoryReader.connectSsl(DirectoryReader.java:96)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.repository.directory.DirectoryReader.connect(DirectoryReader.java:106)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.repository.IASSchema.getOIDVersion(IASSchema.java:341)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.repository.SchemaManager.getOIDVersion(SchemaManager.java:279)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.reports.config.ReportsAppEntityAdder.makeOidEntry(Unknown Source)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.reports.config.ReportsConfigHelper.createReportsAppEntity(Unknown Source)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.reports.config.ReportsConfigHelper.startConfiguration(Unknown Source)

[Tue Dec 29 12:57:51 2009 INFO] oracle.ias.reports.config.ReportsConfig.main(Unknown Source)

[Tue Dec 29 12:57:51 2009 INFO] Error during Reports OID integration

[Tue Dec 29 12:57:51 2009 INFO] Reports OID integration failed

[Tue Dec 29 12:57:52 2009 INFO] Starting file instantiation

[Tue Dec 29 12:57:52 2009 INFO] File instantiation failed

[Tue Dec 29 12:57:52 2009 INFO] Registering Reports as a database provider

[Tue Dec 29 12:57:52 2009 INFO] Reports registration was successful

[Tue Dec 29 12:57:52 2009 INFO] Starting EM integration

[Tue Dec 29 12:57:53 2009 INFO] Deleting target:FR_AS_8.Acmpsrvtr8.auh.police_Reports_Server:rep_acmpsrvtr3_FRHome

[Tue Dec 29 12:57:53 2009 INFO] 0 [main] WARN emSDK.config - Warning: could not find:emtgtctl.bat

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteSingleTargetFromCentralHomePriv(TargetInstaller.java:5043)

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteTargetFromCentralHomes(TargetInstaller.java:1557)

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteTargetInt(TargetInstaller.java:2200)

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteTarget(TargetInstaller.java:2103)

[Tue Dec 29 12:57:53 2009 INFO] oracle.ias.reports.config.ReportsConfigHelper.deleteTarget(Unknown Source)

[Tue Dec 29 12:57:53 2009 INFO] oracle.ias.reports.config.ReportsConfigHelper.startConfiguration(Unknown Source)

[Tue Dec 29 12:57:53 2009 INFO] oracle.ias.reports.config.ReportsConfig.main(Unknown Source)

[Tue Dec 29 12:57:53 2009 INFO] Error while updating file : targets.xml

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteSingleTargetFromCentralHomePriv(TargetInstaller.java:5043)

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteTargetFromCentralHomes(TargetInstaller.java:1557)

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteTargetInt(TargetInstaller.java:2200)

[Tue Dec 29 12:57:53 2009 INFO] oracle.sysman.emSDK.conf.TargetInstaller.deleteTarget(TargetInstaller.java:2103)

[Tue Dec 29 12:57:53 2009 INFO] oracle.ias.reports.config.ReportsConfigHelper.deleteTarget(Unknown Source)

[Tue Dec 29 12:57:53 2009 INFO] oracle.ias.reports.config.ReportsConfigHelper.startConfiguration(Unknown Source)

[Tue Dec 29 12:57:53 2009 INFO] oracle.ias.reports.config.ReportsConfig.main(Unknown Source)

[Tue Dec 29 12:57:53 2009 INFO] EM integration failed

[Tue Dec 29 12:57:53 2009 INFO] Reports configuration ended at: Tue Dec 29 12:57:53 GST 2009

[Tue Dec 29 12:57:53 2009 INFO] Reports Configuration failed

[Tue Dec 29 12:57:53 2009 INFO]
_________ ABORTING CLONE OPERATION ________

[Tue Dec 29 12:57:53 2009 INFO] An error has occured. Aborting the clone operation.
[Tue Dec 29 12:57:53 2009 INFO] Please refer to the error log file D:\oracle\FR_AS\clone\logs\error1262076930.log for details.
[Tue Dec 29 12:57:53 2009 INFO]
______________________________________________

Solution:

1. Apply Patches

Installed Patch List:
=====================
1) Patch 4711967
[ Bug fixes: 4711967 ]
2) Patch 4386413
[ Bug fixes: 4386413 ]

2. Run the prepare_clone.pl script again

3. Edit the $ORACLE_HOME/clone/config/source.properties and change the following lines:

oracle_home_name=Not yet set!!
host=Not yet set!!

to:

oracle_home_name=<source_oracle_home_name>host=<source_host.domain>

4. Tar up the source ORACLE_HOME and copy it to the machine where you want the clone to reside

5. Run:
perl clone.pl ORACLE_HOME=<path_where_tar_was_extracted> ORACLE_HOME_NAME=<oracle_home_name> -instance <instance_name>

References:

Note. 368727.1 - Problems Cloning a Standalone Forms and Reports installation

Get Oracle Certifications for all Exams
Free Online Exams.com

udump generates after control autobackup

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description: Starting control autobackup genrates trace files and messages on the alert log file

alert.log showing the below;Comments
--------
Starting control autobackup
Tue Nov 10 09:20:55 2009
Errors in file \udump\dnadb_ora_3384.trc:

Tue Nov 10 09:20:55 2009
Errors in file \udump\dnadb_ora_3384.trc:

Tue Nov 10 09:20:55 2009
Errors in file \udump\dnadb_ora_3384.trc:

Control autobackup written to DISK device
handle 'E:\BACKUP\RMAN\DNADB\BACKUPSETS\CONTROL_DNADB_C-3965614685-20091110-00.CTL'
Tue Nov 10 09:21:08 2009

Trace file \udump\dnadb_ora_2168.trc shows the following;

FileComment
-----------
Redo thread mounted by this instance: 1

Oracle process number: 23

Windows thread id: 2168, image: ORACLE.EXE (SHAD)

*** 2009-11-16 21:05:59.529
*** ACTION NAME:(0000022 STARTED111) 2009-11-16 21:05:59.404
*** MODULE NAME:(backup full datafile) 2009-11-16 21:05:59.404
*** SERVICE NAME:(SYS$USERS) 2009-11-16 21:05:59.404
*** SESSION ID:(170.14906) 2009-11-16 21:05:59.404
*** 2009-11-16 21:06:22.357
*** ACTION NAME:(0000050 STARTED111) 2009-11-16 21:06:22.357
*** MODULE NAME:(backup archivelog) 2009-11-16 21:06:22.357

Solution:

From the alert.log and trace file there is no error message. Also the control file auto backup completed successfully.
hence you can ignore this message

Get Oracle Certifications for all Exams
Free Online Exams.com

'Assertion Failed WExpression: Window !=(ixobj *)0" on Oracle Forms 10.1.2.0.2 version

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

4. Tar up the source ORACLE_HOME and copy it to the machine where you want the clone to reside

Get Oracle Certifications for all Exams
Free Online Exams.com

ORA-00600: internal error code, arguments: [17059], [0x4633429D8]

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description: Database Crashes

Symptoms:

Database hangs frequently, Database Alert Log file shows "ORA-00600: internal error code, arguments: [17059], [0x4633429D8]"

Many trace files generated causing shortage on storage.

Alert Log file shows:

Trace files shows :

System Error Log shows:

Solution:

1. From the error log, it is clear that there is no swap space, thats the reason for getting the error. involve your system administrators to resolve this problem

2. set the stack size to unlimited

3. Apply Interim patch 5705795

Get Oracle Certifications for all Exams
Free Online Exams.com

ORA-07445: exception encountered: core dump [ddfnetCFull()+2040] [SIGSEGV] [Address not mapped to o bject] [0xFFFFFFFF7B4800A0] [] []

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description:

Getting the following error while inserting the records over the dblink:

ORA-07445: exception encountered: core dump [ddfnetCFull()+2040] [SIGSEGV] [Address not mapped to o
bject] [0xFFFFFFFF7B4800A0] [] []

Symptoms:

Database Alert Files shows:

Errors in file /oradg2/orasys/admin/adp2/udump/adp_ora_6440.trc:
ORA-07445: exception encountered: core dump [ddfnetCFull()+2040] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFF7B1800A0] [] []

Database Trace File shows:

*** SERVICE NAME:(SYS$USERS) 2009-12-22 07:29:48.796
*** SESSION ID:(2256.34220) 2009-12-22 07:29:48.796
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0xffffffff7b4800a0, PC: [0x102450e98, ddfnetCFull()+2040]
*** 2009-12-22 07:29:48.840
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ddfnetCFull()+2040] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFF7B4800A0] [] []
Current SQL statement for this session:

INSERT INTO Table_Name From Table_Name@DBLINK

Explanation:

Problem caused due to in-doubt transactions exists in the database.

Solution:

purging pending transactions would rectify ora-7445

1. Identify the id of the transaction:

SQL> SELECT LOCAL_TRAN_ID, GLOBAL_TRAN_ID FROM DBA_2PC_PENDING;

If there are entries returned by the above query then,

2. Try to commit/ rollback these failed transactions :

To Commit:

SQL>commit force;

To Rollback :

SQL> rollback force;

3. If still no success, then you need to purge these transactions:

SQL> alter system enable distributed recovery;

SQL> alter system set "_smu_debug_mode" = 4;
SQL> EXECUTE DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY('<transaction_id>');
SQL> COMMIT;

4. Confirm that the transaction has been purged:

SQL> SELECT LOCAL_TRAN_ID, GLOBAL_TRAN_ID FROM DBA_2PC_PENDING;

Reference :

Note.126069.1 Manually Resolving In-Doubt Transactions Different Scenarios
Note.401302.1 How To Resolve Stranded DBA_2PC_PENDING Entries
Note.100664.1 How to Troubleshoot Distributed Transactions

Get Oracle Certifications for all Exams
Free Online Exams.com

ORA-00600: internal error code, arguments: [17059], [0x4633429D8], [], [], [], [], [], []

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem Description: Patch 4367986 conflicting with already installed Patch 5705795.

Getting ORA-600 [17059] on the database alert log file

Problem Explanation:

ORA-600 [17059] is a memory corruption error that occurs while building a table to hold the list of child cursor dependencies relating to a given parent cursor and we exceed the maximum possible size of the table.

identify why so many child cursors have been created, can you please check V$SQLAREA for a statement using a excessive number of child cursors, e.g.:

connect / as sysdba
spool cursor_info.txt
select version_count, sql_id, sql_text from v$sqlarea
where version_count > 5000 order by version_count;

and then for the statement with the largest version count, identify why they are not getting shared from V$SQL_SHARED_CURSOR, e.g.:

select * from v$sql_shared_cursor where address in (
select address from v$sqlarea where sql_id = '<SQL_ID from above>');

Alert Log File shows;

Mon Jan 18 16:32:47 2010
Errors in file /orasys/ipay/udump/ipay_ora_24069.trc:
ORA-00600: internal error code, arguments: [17059], [0x4633429D8], [], [], [], [], [], []
Mon Jan 18 16:32:52 2010
Errors in file /orasys/ipay/udump/ipay_ora_24071.trc:
ORA-00600: internal error code, arguments: [17059], [0x4633429D8], [], [], [], [], [], []
Mon Jan 18 16:32:55 2010
Errors in file /orasys/ipay/udump/ipay_ora_24117.trc:
ORA-00600: internal error code, arguments: [17059], [0x4633429D8], [], [], [], [], [], []
Mon Jan 18 16:32:58 2010
Errors in file /orasys/ipay/udump/ipay_ora_24073.trc:

Trace Files Shows:

parent=463342af0 maxchild=32770 plk=46e81ca48 ppn=n
cursor instantiation=ffffffff7a730318 used=1263817964
child#32769(0) pcs=40d6be768
clk=0 ci=0 pn=0 ctx=0
kgsccflg=0 llk[ffffffff7a730320,ffffffff7a730320] idx=0
xscflg=28 fl2=0 fl3=82080 fl4=0
sharing failure(s)=400
No bind info: cannot access child information block
and the oacdefs are not stored in the instantiation
Frames pfr 0 siz=0 efr 0 siz=0
Cursor frame dump
Session cached cursors

Workaround:

you can stop the ORA-600 [17059] errors occurring by flushing the shared pool using:

connect / as sysdba
alter system flush shared_pool;
alter system flush shared_pool;
alter system flush shared_pool;
exit

Solution:

Patch 5705795 would rectify the issue however it conflicts with patch 4367986.

A merged version of the patches is available for download from My Oracle Support as patch 7007477

Get Oracle Certifications for all Exams
Free Online Exams.com

Users cannot run arabic FSG reports in gl or report manager

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem:

Cannot view XML input using XSl stylesheet. Please correct the error
and click Refresh button, or try again later

An invalid character was found in text content
Error processing resource

"FSG: Database Codeset" profile does not exist while it is mandatory where the codeset is non utf-8.
Running the Program - publish FSG report:
RGFSGXML module: Program - Publish FSG Report

+------------- 1) PUBLISH -------------+
Beginning post-processing of request 521394 on node ERPDEV at 04-FEB-2010 14:19:05.
Post-processing of request 521394 failed at 04-FEB-2010 14:19:16 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.

Publisher log shows the error:
[2/4/10 2:19:16 PM] [UNEXPECTED] [28569:RT521394] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:517)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:224)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
at
.....

oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
Caused by: java.io.UTFDataFormatException: Invalid UTF8 encoding.

Codeset is:
ISO-8859-6

"FSG: Database Codeset" profile does not exist.

This is causing the issue as XML is using a wrong codeset to generate the output.
The logfile confirms:
oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
Caused by: java.io.UTFDataFormatException: Invalid UTF8 encoding.

Explanation:

On : 12.0.6 version, Core Functionality

When attempting to submit and publish an FSG report in arabic, the following error occurs.
Submitting this report shows waring in completion.
Also Submitting the report in report manager seems to complete fine, but little squares are shown instead of arabic data

The profile is mandatory when the codeset is a non utf-8 one.

Solution: Define "FSG: Database Codeset" profile, point it to the correct codeset and retest.

1. Change the setup as following:
Go to "Application Developer" -> Profile and create a new profile with:
Name: RG_XML_CODESET
Application: Application Report Generator
User Profile Name: FSG: Database Codeset
Description: Database Codeset
Active Dates Start: 01/01/1951
All check boxes should be checked.
Save

2. Go to "System Administrator" -> Profiles -> System and query all profiles with name starting with "FSG%".
Go to the profile "FSG: Database Codeset" , enter your codeset value ISO-8859-6 at the site level and save.

Reference:

Note 470233.1 'Generating Fsg Xml Publisher Report Ends in 'Invalid UTF8 Encoding' Error' -is relevant for the issue, shows how to check the codeset. This is most probably set incorrectly.

Get Oracle Certifications for all Exams
Free Online Exams.com