Please visit my new domain at http://ediyanto.co.cc

C U there…

Update (as of 08-Nov-2009):

- Oracle Top-N Query
- Bersyukurlah…
- Cinta Sejati
- Nice Story
- 5 Tips Agar Tak Mudah Lelah
- Belajar dari Alphabet
- How To Get the List of All Responsibilities Assigned To A User
- Query To Find Multi-Org Is Enabled Or Not
- How To Find A Patch Is Applied For A Bug
- Excel Limitations on Images
- BLOB Images in XML Publisher
- Today Is Beautiful Day And I Cannot See It
- Scheduled Ship Date Time Always Reset To 23:59:00 in Oracle Apps R11i
- Tandingan Antar Berkumis
- Hati yang Luka
- Mr. Pig
- Changing LOV using Forms Personalization on Oracle Apps R12
- Starting VMware Server Hangs/Crashes on Windows Vista
- Where Context XML File in Oracle Apps R12?
- Kekuatan Pikiran

Cause: Failed to allocate an extent of the required number of blocks for a temporary segment in the tablespace indicated.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

MetaLink has a very detailed and informative article concerning ORA-01652 and RAC.  There is some troubleshooting required with ORA-01652 in RAC because there are two common causes in this area.

1. ORA-01652 may occur because there is simply no space available in the temp tablespace of which is being used.
2. ORA-01652 may have to do with the local temp segment not being able to extent space even though there is space in other instances.

To troubleshoot for ORA-01652,  and find out which of the above scenarios are causing ORA-01652 use this query offered by MetaLink:

select sum(free_blocks)
from gv$sort_segment
where tablespace_name = ‘<TEMP TABLESPACE NAME>’

You will know that the first scenario is causing ORA-01652 to be thrown if the free block reads ‘0′ because it signifies that there is no free space.

If there is a good amount of space, you know that there is another cause for ORA-01652, and it is probably the second scenario.  It is important to note that in a non-RAC environment, local instances are not able to extend the temp segments.

In sever cases, a slowdown may occur, in which you might want try one of the following work-arounds:

1. Increase size of the temp tablespace
2. Increase sort_area_size and/or pga_aggregate_target

If ORA-01652 is causing the slowdown, SMON will probably not be able to process the sort segment requests, you  should try to diagnose the contention:

• Output from the following query periodically during the problem:
  select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks
  from gv$sort_segment;
• Global hang analyze and systemstate dumps

Reference: Oracle Error Tips by Burleson Consulting

Three possible errors can occur as below:

• The Output Post Processor is not running or does not pick up the request

…
+————- 1) PUBLISH ————-+
Unable to find an Output Post Processor service to post-process request [request_id].

Check that the Output Post Processor service is running.
+————————————–+
…

Solutions:
* Verify that the Output Post Processor is enabled and active.
* If confirmed, retrieve the OPP log file either via the Forms application or via the Oracle Application Manager.
- Via the Forms application:

1. Login to the application as SYSADMIN
2. Responsibility: System Administrator
3. Function: Concurrent –> Manager –> Administration
4. Select the Output Post Processor
5. Click on the Processes button
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Manager Log button to open the Output Post Processor log file

- Via the Oracle Application Manager

1. Login to the application as SYSADMIN
2. Responsibility: System Administration
3. Function: Oracle Applications Manager –> Concurrent Managers
4. Select the Output Post Processor Service and click on View Details
5. Click on View Processes
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Log button to open the Output Post Processor log file

• The Output Post Processor is running but has not picked up the request

...
+------------- 1) PUBLISH -------------+
The Output Post-processor is running but has not picked up
this request.No further attempts will be made to post-process
this request, and the request will be marked with Warning status.
Setting the profile option Concurrent: OPP Response Timeout
to a higher value may be necessary.
+--------------------------------------+
...

By default a timeout will occur if it takes longer then 120 seconds (2 min.) for the Output Post Processor to pick up the request from the Concurrent Manager process. In that case, the Concurrent Request will complete with status Warning and the Request log file will contain error message like above.

Solutions:
* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Response Timeout‘.

• The concurrent manager has timed out waiting for the Output Post-processor to finish this request

…
+————- 1) PUBLISH ————-+
The concurrent manager has timed out waiting for the Output Post-processor
to finish this request.

Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile.
+————————————–+
…

The concurrent manager process has successfully invoked the OPP but it a timeout is encountered as the OPP takes too long to complete the job.

The time that this takes will depends on various elements such as:

• size of the XML Data File
• complexity of the template
• performance of the server
• ….

By default a timeout will occur if it takes longer then 300 seconds (5 min.) for the XML Publisher engine to generate the output file. The Concurrent Request will complete with status Warning and the Request log file will contain error message like above.

Solutions:
* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Process Timeout‘.

When you submit the XML Report Publisher Program (XDOREPPB) you are prompted to select the Request ID for the data generation program. The LoV for this parameter is not being populated due to an incorrect profile option reference.

To work around this issue, you must change the references to the incorrect profile option in the XDO_REPORT_REQUEST_ID value set as follows:

1. Using the System Administrator responsibility, open the Value Set form. Navigation: Application > Validation > Set.
2. Query value set name XDO_REPORT_REQUEST_ID.
3. Click Edit Information.
4. Modify Where/Order By as follows:
   

Current:

WHERE ( ( FND_PROFILE.VALUE(‘CONC_REPORT_ACCESS_LEVEL’) = ‘U’
AND R.REQUESTED_BY = :$PROFILES$.USER_ID ) or
( FND_PROFILE.VALUE(‘CONC_REPORT_ACCESS_LEVEL’) = ‘R’
AND R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID ) )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE=’XML’
AND R.STATUS_CODE not in (‘E’, ‘D’, ‘T’, ‘X’)
ORDER BY R.REQUEST_ID DESC

Modified to:

WHERE (R.REQUESTED_BY = :$PROFILES$.USER_ID or
R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE=’XML’
AND R.STATUS_CODE not in (‘E’, ‘D’, ‘T’, ‘X’)
ORDER BY R.REQUEST_ID DESC

Reference Note:404928.1

After entering the address details in Create Customer Form, get error when saving:
“APP-AR-96282:Error The following SQL error occured
ORA-00001 : unique constraint (AR.HZ_CUST_ACCT_SITES_U2) violated”

Cause

The current value of sequence hz_cust_acct_sites_s is smaller than the existing data in hz_cust_acct_sites_all.orig_system_reference.

select hz_cust_acct_sites_s.currval from dual;
returns
3188

SQL> select column_name from dba_ind_columns where index_name=’HZ_CUST_ACCT_SITES_U2′;
COLUMN_NAME
ORIG_SYSTEM_REFERENCE
ORG_ID

But client has records in hz_cust_acct_sites_all table with value greater than 901000 for orig_system_reference column.

Solution

1. DROP sequence ar.hz_cust_acct_sites_s;
2. CREATE SEQUENCE AR.HZ_CUST_ACCT_SITES_S
START WITH 10001
MAXVALUE 900999
MINVALUE 10001
NOCYCLE
NOCACHE;
Note: the start value, minimum/maximum value depends on your needs and  the sequence must be set higher than the largest value stored in HZ_CUST_ACCT_SITES_All.orig_system_reference.

Reference: Doc ID 388728.1

When attempting to apply Patch 6502082 – 11i.AD.I.6, the following error occurs

AutoPatch error:
Error while executing statement

AutoPatch error:
ORA-06550: line 3, column 10:
PLS-00302: component ‘IS_PATCH_APPLIED2′ must be declared
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored

The issue is caused by the following setup:

Following package versions for package APPS.AD_PATCH are not created.
$AD_TOP/patch/115/sql adphpchb.pls   115.16
$AD_TOP/patch/115/sql adphpchs.pls   115.11

To implement the solution, please execute the following steps:
1. Go to $AD_TOP/patch/115/sql
2. Check the version of adphpchs.pls and adphpchb.pls
adident Header $AD_TOP/patch/115/sql/adphpch*.pls
It should be -
$AD_TOP/patch/115/sql/adphpchs.pls (version 115.11)
$AD_TOP/patch/115/sql/adphpchb.pls (version 115.16)

3. If it is not there, run them from <patch-top-directory>/ad/patch/115/sql
4. Once the proper versions are available, run them from sqlplus as APPS user
SQL> @adphpchs.pls
SQL> @adphpchb.pls

5. Check the version and status once again
SQL> select status, object_type, owner from dba_objects where object_name = ‘AD_PATCH’;
SQL> select text from dba_source where line = 2 and name = ‘AD_PATCH’;

6. Retest adpatch from beginning
7. Migrate the solution to appropriate environment

Reference: Doc ID 556785.1

While running XML Publisher report for EXCEL output, the Concurrent Program has the error message :

“ORA-1403: no data found”

The cause of this problem has been identified in Bug 4396843 by Metalink.

The output of the report can be viewed from menu Request > Monitor through System Administration Responsibility or you can solve this problem by 2 way :

1. Change the length of oftype variable from varchar2(4) to varchar2(5) in editor_pkg2.browser_show() of FNDCONC.PLL. Because output type “EXCEL” can’t be strored in that variable as it exceeds the size of the variable. After that, compile PLL with this syntax: “f60gen module=FNDCONC.pll userid=apps/apps module_type=library batch=yes output_file=FNDCONC.plx compile_all=special“
2. Apply patch 4396842 or later

1. Set the following profile options for the user who performs the Home Page personalization: Personalize Self Service Definition – Yes and FND: Personalization Region Link - Yes
2. Login to Applications Home Page and select the ‘Personalize Page’ link.
3. In the search option look for the “Row Layout” value in the list of values
   (style field) and click on GO button.
4. In the “Row Layout: Home Content Row” row, click on Personalize icon.
5. Change the rendered attribute to True in the “Applications Home Page” column.
6. Click on Apply, then Log off and Log in again. The worklist should appear this time.

When you try to install the Oracle Workflow Builder on Vista, the following error appears:

Starting Oracle Universal Installer…
Checking installer requirements…
Checking operating system version: must be 4.0, 5.0, 5.1 or 5.2.    Actual 6.0
Failed <<<<

Oracle Workflow Builder Client has not been Certified yet to run on Windows Vista.
To configure the compatibility mode for an application, just locate the installation directory and right click on the .exe, selecting Properties from the menu.

1. Navigate to the WF Builder installer (setup.exe) in the file system
2. Right-Click on the “setup.exe” > then go to Properties
3. Check Compatibility Mode and  Select “Windows XP (Service Pack 2)”
4. Now restart the Installer for the Workflow Builder

Reference:
http://www.howtogeek.com/howto/windows-vista/using-windows-vista-compatibility-mode/
Note 551484.1 – Unable To Install Workflow Builder On Microsoft Vista