Be very careful when using tar

I often use tar to make cold database file backup since one big file is faster to copy via network. One time I accidentally entered wrong command on tar, I entered 'tar cvfj /u01/oracle/DEV/db/apps_st/data/* data.tar.bz2'. The tar ran fine until encountered error at the end with no tar file created. Then I realized that the tar command should be 'tar cvfj data.tar.bz2 /u01/oracle/DEV/db/apps_st/data/'.
When I tried to start the DEV database instance, it woudn't start. It said a_archive01 is corrupted (I don't remember the exact error). Luckily it was a DEV instance, I can easily clone again from production instace.
I haven't tried it for second time to make sure it was wrong tar command that made the corruption, but still it is better to be more careful.

Exception trying to access the repository. java.sql.SQLException: ORA-02291: integrity constraint (SYSMAN.MGMT_ARU_FAM_PRD_PRD_FK) violated

Problem: Trying to refresh from My Oracle Support on Grid Control 10.2.0.5 and receive Exception trying to access the repository. java.sql.SQLException: ORA-02291: integrity constraint (SYSMAN.MGMT_ARU_FAM_PRD_PRD_FK) violated - parent key not found.
Solution: Go to Deployment tab, select Provisioning > Administration. On Software Library Configuration section, select Purge to purge deleted entities.

Clone E-business suite and grid control problem

When discovering oracle applications on grid control 10.2.05, you encounter error "Wrong System Name" or "Waited for five minutes" and you see the context file mentioned on the log is not correct, then
1. Source your environment for EBusiness Suite instance.
2. Run sqlplus as apps user
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
3. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers, to repopulate the required system tables.
4. Bounce Agent.
5. Retry to discover EBusiness Suite instance.

Grid Agent URL connection interrupted

When trying to open agent URL, something like https://host:3872/emd/main, you receive connection interrupted message on your browser. Go to your agent home/bin directory.
> ./emctl stop agent
> ./emctl secure agent
> ./emctl start agent

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

When you execute "emctl upload" command, you receive "EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..."
Check your repository URL, you probably use secure connection to OMS, change the URL to https://oms_server:1159/em/upload. Restart your agent.

Patching Setup - My Oracle Support authorization failed

When you receive this message when setup patching on Grid Control 10.2.0.5: "My Oracle Support authorization failed. - Although metalink credentials are correct and successfully validated, an error occurred while downloading a sample patch from the patch url specified. Please check log files for details." then go see the log file on $ORACLE_HOME/sysman/log/emoms.log.
Just see some lines at the end of the file, use tail -n 100 emoms.log.
If you see ORA-14400, then using sqlplus and as sysman, run this on sqlplus:
exec emd_maintenance.analyze_emd_schema(‘SYSMAN’);

Unable to compile invalid object ORA-04030

Solution from http://oracledbas.blogspot.com/2009/02/ora-04030-out-of-process-memory.html

SQL> alter package apps.XLA_00200_AAD_S_000010_PKG COMPILE BODY;
alter package apps.XLA_00200_AAD_S_000010_PKG COMPILE BODY
*
ERROR at line 1:
ORA-04030: out of process memory when trying to allocate 4108 bytes (PLS
non-lib hp,pdzgM64_New_Link)

Solution
1.SQL>select object_name,object_type from dba_objects where status='INVALID';
OBJECT_NAME OBJECT_TYPE
----------------------------------- -------------------
XLA_00200_AAD_S_000010_PKG PACKAGE BODY
XLA_00200_AAD_S_000011_PKG PACKAGE BODY

2. SQL> alter system set plsql_optimize_level =0;
System altered.

3.SQL> alter package apps.XLA_00200_AAD_S_000010_PKG COMPILE BODY;
Package body altered.

4.SQL> alter package apps.XLA_00200_AAD_S_0000011_PKG COMPILE BODY;
Package body altered.

5.SQL> alter system set plsql_optimize_level =2;
System altered.

Don't forget to turn SLA: Enable Diagnostic off

If you need to set SLA: Enable Diagnostic to yes, then you must set it back to no right after you run your SLA request. If you forget to do so, your database will grow rapidly. Mine has grown 1.6 Gb in only one day!

Blank Page Accessing R12 - 'Missing class: _RF' in OACore application.log

Applies to:

Oracle Applications Technology Stack - Version: 12.0
This problem can occur on any platform.

Symptoms

On 12.0, trying to connect to the home page (http://<server>.<domain>.<port#>), redirects to http://<server>.<domain>.<port#>/OA_HTML/AppsLocalLogin.jsp which shows a blank page.

Further more, the application.log file of the OACore OC4J shows the following error stack:

javax.servlet.ServletException: oracle.classloader.util.AnnotatedClassNotFoundException:

Missing class: _RF

Dependent class: oracle.jsp.runtimev2.JspPageInfo
Loader: oc4j:10.1.3
Code-Source: /oracle/apps/tech_st/10.1.3/j2ee/home/lib/ojsp.jar
Configuration: <code-source> in META-INF/boot.xml in /oracle/apps/tech_st/10.1.3/j2ee/home/oc4j.jar

This load was initiated at oacore.web.html.jsp8892557:0.0.0 using the loadClass() method.

The missing class is not available from any code-source or loader in the system.
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:387)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:478)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:401)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:627)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)

Cause

JSPs need recompilation.

Solution

-- To implement the solution, please execute the following steps:
Either:
A. Set the JSP compilation to Automatic using the following steps:
1. Use the vi editor to edit the $CONTEXT_NAME.xml context file used by AutoConfig and change the value for "s_jsp_main_mode" from "justrun" to "recompile" (without the double quotes)

NOTE
~~~~~
Backup the context file before editing it.

2. Run Autoconfig to propagate the changes to the configuration files.

3. Verify that now the
$INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml has

<init-param>
<param-name>main_mode</param-name>
<param-value>recompile</param-value>
</init-param>

4. Restart the Middle Tier services and access the applications to load JSP's which will cause them to be recompiled on the run.

5. After successfully accessing the applications, use the vi editor to edit the $CONTEXT_NAME.xml context file used by AutoConfig and revert the value for "s_jsp_main_mode" to "justrun" (without the double quotes) in order not to hamper the performance of your system.

6. Run AutoConfig to propagate the changes.

NOTE
~~~~~

You can always use the next option to compile JSP's manually at any time.

OR
B. Recompile the JSP manually using the following steps:
1. Telnet to your server using applmgr user and source the environment by running the script:

/oracle/apps/apps_st/appl/APPS<SID>_<host>.env

2. Run the commands

UNIX

cd $FND_TOP/patch/115/bin
perl ojspCompile.pl --compile --flush -p 2

Windows

cd %FND_TOP%\patch\115\bin
- perl -x ojspCompile.pl –compile –flush

3. Restart the Middle Tier services.

$5 discount coupon

I have a $5 discount coupon from play-asia.com. But I won't use it because it has minimum order value $50 to use. You can use it if you want, the code is: WP-FKV-YIF. This coupon expires on August 30th, 2009. Just click below to visit play-asia.com. Don't forget to leave a comment when you have used it.

Ora-07445: Core Dump [Ioc_pin_shared_executable_object()+796]

Applies to:

Oracle Server - Enterprise Edition - Version: 11.1.0.6
This problem can occur on any platform.

Symptoms

You can find the following exception in the alert log.

Tue Feb 12 15:00:02 2008
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x1063BAD1C, ioc_pin_shared_executable_object()+796]
Tue Feb 12 15:00:02 2008
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x1063BAD1C, ioc_pin_shared_executable_object()+796]
Errors in file /u00/app/oracle/diag/rdbms/ORCL/ORCL/trace/ORCL_m000_19716.trc (incident=33881):
ORA-07445: exception encountered: core dump [ioc_pin_shared_executable_object()+796] [SIGSEGV] [ADDR:0x0] [PC:0x1063BAD1C] [Address not mapped to object] []
Incident details in: /u00/app/oracle/diag/rdbms/ORCL/ORCL/incident/incdir_33881/ORCL_m000_19716_i33881.trc
Errors in file /u00/app/oracle/diag/rdbms/ORCL/ORCL/trace/ORCL_j000_19714.trc (incident=33873):
ORA-07445: exception encountered: core dump [ioc_pin_shared_executable_object()+796] [SIGSEGV] [ADDR:0x0] [PC:0x1063BAD1C] [Address not mapped to object] []
Incident details in: /u00/app/oracle/diag/rdbms/ORCL/ORCL/incident/incdir_33873/ORCL_j000_19714_i33873.trc
Tue Feb 12 15:00:04 2008
Trace dumping is performing id=[cdmp_20080212150004]

Cause

Bug 6325878 - USING VLM & RAMFS W/11G CAUSES ORA-7445 [IOC_PIN_SHARED_EXECUTABLE_OBJECT]

RELEASE NOTES: 
Oracle VLM configuration which instructs dba to mount /dev/shm as ramfs was incompatible with Oracle Java JIT

REDISCOVERY INFORMATION: 
Mounting /dev/shm as ramfs and start the database with JIT not disabled 

WORKAROUND: 
Two workarounds. 
1. Do not mount /dev/shm as ramfs and hence do not use VLM which requires it. 
2. Disable JIT and do not use pl/sql native compilation.

Solution

To workaround the issue, set JAVA_JIT_ENABLED=FALSE at parameter file and bounce the instance.

SQL> alter system set JAVA_JIT_ENABLED= FALSE scope = both;

System altered.

SQL> shutdown immediate
SQL> startup

SQL> show parameter JAVA_JIT_ENABLED
NAME             TYPE    VALUE
---------------- ------- ------------------------------
java_jit_enabled boolean FALSE

Using FND Log

Set the following Profile Options at the User Level:

FND: Debug Log Enabled -> Yes
FND: Debug Log Level -> Statement
FND: Debug Log Module -> %

1) Run the following sql query:

Select max(log_sequence) from fnd_log_messages;

2) Simulate the error process.

3) Provide the log file using the following query:

Select module, message_text from fnd_log_messages
Where log_sequence > 'put max log_sequence from above'
order by log_sequence;

Do not run adpatch with only one worker

When running adpatch, when asked for number of workers, do not enter 1. Sometimes an error needed for adpatch is included on the same patch. So if error occured, the job will be deferred if there are more than one worker. After that another worker will continue to work and the error fixed. When adpatch retry the failed job, it will be fixed.
If only one worker assigned, when error occurred, adpatch will stop, no job is deferred, so the error must be fixed outside adpatch.

Living in the desert

I have never thought of living in the desert. It's a little bit scary. But after viewing Desert Ridge Realtor website, it's interesting to see houses on desert.
The website gives you facilities to search and select houses located in the desert. Even 2D and 3D maps also provided.
If you like to have a house in the desert, you should visit this website.

Unable to cancel invoice due to tax distribution variance

CAUSE DETERMINATION
===================
The cause of the issue is invalid / incorrect data in ap_invoice_lines_all
and ap_invoice_distributions_all .

CAUSE JUSTIFICATION
===================
The following bug was logged for this specific customer to receive a datafix
from Oracle Development:
Bug.8357578: UNABLE TO CANCEL INVOICE DUE TO TAX DISTRIBUTION VARIANCE
Oracle Development stated that the issue is due to invalid / incorrect data.

The AP List identified the issue data.

PROPOSED SOLUTION(S)
====================
Apply a datafix to correct invalid / incorrect data in ap_invoice_lines_all
and
ap_invoice_distributions_all.

PROPOSED SOLUTION JUSTIFICATION(S)
==================================
The following bug was logged for this specific customer to receive a datafix
from Oracle
Development:
Bug.8357578: UNABLE TO CANCEL INVOICE DUE TO TAX DISTRIBUTION VARIANCE
Oracle Development stated that the issue is due to invalid / incorrect data.
Oracle Development provided a datafix.
The datafix will do the following:
1. correct the data in ap_invoice_lines_all and
ap_invoice_distributions_all.

SOLUTION / ACTION PLAN
======================
-- To implement the solution, please execute the following steps::
Execute the below SQL and commit the changes:

create table aid_bkp as
select *
from ap_invoice_distributions_all
where invoice_id = 10490
and line_type_lookup_code like '%TAX%';

create table ail_bkp as
select *
from ap_invoice_lines_all
where invoice_id = 10490
and line_type_lookup_code like '%TAX%';

delete
from ap_invoice_distributions_all
where invoice_id = 10490
and line_type_lookup_code like '%TAX%';

delete
from ap_invoice_lines_all
where invoice_id = 10490
and line_type_lookup_code like '%TAX%';

commit;

Agent status unavailable on enterprise manager

Enterprise Manager, Database Control 10g shows the status 'Agent
unavailable' even though the agent and database are up an
running.
To fix that error:
Recreate the DB Control Configuration Files only (leave Repository intact)
In 10.2, the EMCA commands can be used to reconfigure the existing installs
without removing them first. Run the command:
<ORACLE_HOME>/bin/emca -config dbcontrol db

Error ORA-04030 : out of process memory when trying to allocate 4108 bytes when compiling package

Applies to:

Oracle Payables - Version: 12.0.1
This problem can occur on any platform.

Symptoms

In  Release 12 instances , the package XLA_00200_AAD_S_000010_PKG fails to compile by firing the Error ORA-04030 : out of process memory when trying to allocate 4108 bytes.

STEPS
The issue can be reproduced at will with the following steps:
1. Change database initialization parameters.
2. Convert pl/sql code type to native following steps under
"Modifying the Entire Database for PL/SQL Native or Interpreted Compilation (page 11-29)"
of "Oracle Database PL/SQL User's Guide and Reference 10g Release 2 (10.2)".
3. Recompile package body XLA_00200_AAD_S_000010_PKG.

Changes

Changed the database initialization parameter plsql_code_type to 'native' as per Note 396009.1 Database Initialization Parameters for Oracle Applications Release 12 and converted the pl/sql code to native as per Oracle Database PL/SQL User's Guide and Reference.

Cause

The issue is reported in the internal unpublished Bug which interprets the reason of the failure as follows:

Package size is more than 130K lines which make the sql optimization use too much memory.   The system generated packages are not shipped with the product and they depend on the customer setup so packages can vary in size from one situation to another.

Solution

Action Plan:

1.Set the plsql_optimize_level to 0 before compiling the Package by doing the following:

SQL>alter system set plsql_optimize_level =0;

2.Run the alter command to compile the package

3.Set the plsql_optimize_level to 2 after compiling the package as recommended per the following reference Note 396009.1 (Database Initialization Parameters for Oracle Applications Release
12), plsql_optimize_level should be set to '2'

Note :

• Please note that if the plsql_optimize_level is set '0' after the package compilation , this will affect the performance of the application as  it prevents the code from being rearranged at all. 
  
• The Difference between '0' and '2' for plsql_optimize_level.is as follows:
  1. Level 0
     
     Maintains the evaluation order and hence the pattern of side effects, exceptions, and package
     initializations of Oracle9i and earlier releases. Also removes the new semantic identity of
     BINARY_INTEGER and PLS_INTEGER and restores the earlier rules for the evaluation of integer expressions. Although code will run somewhat faster than it did in Oracle9i, use of level 0 will forfeit most of the performance gains of PL/SQL in Oracle Database 10g.
     
  2. Level 2
     
     Applies a wide range of modern optimization techniques beyond those of level 1 including changes which may move source code relatively far from its original location.
     Generally, setting this parameter to 2 pays off in better execution performance. If, however, the compiler runs slowly on a particular source module or if optimization does not make sense for some reason (for example, during rapid turnaround development), then setting this parameter to 1 will result in almost as good a compilation with less use of compile-time resources.

Unable to extend

Applies to:

Oracle Server - Enterprise Edition - Version: 7.0.16.0 to 11.1.0.7
Information in this document applies to any platform.

Purpose

This document can be used to diagnose and resolve space management errors of the type "unable to extend ... by %s in tablespace <name>"  where the 'by %s' extent size is the number of DB blocks.

EXAMPLE ERRORS

ORA-1650: unable to extend rollback segment %s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for a rollback segment in the tablespace.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-1651: unable to extend save undo segment by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for saving undo entries for the indicated offline tablespace.
  Action: Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied.

ORA-1652: unable to extend temp segment by %s in tablespace %s
  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.

ORA-1653: unable to extend table %s.%s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-1654: unable to extend index %s.%s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-1655: unable to extend cluster %s.%s by %s for tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for a cluster segment in tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.


ORA-1683: unable to extend index %s.%s partition %s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for index segment in the tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-1688: unable to extend table %s.%s partition %s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for table segment in the tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-1691: unable to extend lob segment %s.%s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-1692: unable to extend lob segment %s.%s partition %s by %s in tablespace %s
  Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.


ORA-3233: unable to extend table %s.%s subpartition %s by %s in tablespace %s
  Cause: Failed to allocate an extent for table subpartition segment in tablespace.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-3234: unable to extend index %s.%s subpartition %s by %s in tablespace %s
  Cause: Failed to allocate an extent for index subpartition segment in tablespace.
  Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-3238: unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s
   Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated.
   Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

Troubleshooting Details

An "unable to extend" error is raised when there is insufficient contiguous space available to extend a segment.

I. Information needed to resolve UNABLE TO EXTEND errors

In order to address UNABLE TO EXTEND errors the following information is needed:


1. Determine the largest contiguous space available for the tablespace with the error

SELECT max(bytes) FROM dba_free_space WHERE tablespace_name = '<tablespace name>';

The above query returns the largest available contiguous chunk of space.

Please note that if the tablespace you are concerned with is of type TEMPORARY, then please refer to Note 188610.1.

If this query is done immediately after the failure, it will show that the largest contiguous space in the tablespace is smaller than the next extent  the object was trying to allocate.


2. Determine NEXT_EXTENT size

SELECT NEXT_EXTENT, PCT_INCREASE FROM DBA_SEGMENTS WHERE SEGMENT_NAME = <segment name> AND SEGMENT_TYPE = <segment type> AND OWNER = <owner>

<segment type> is usually stated in the error message

Possible Segment Types:

   CLUSTER
   INDEX
   INDEX PARTITION
   LOB PARTITION
   LOBINDEX
   LOBSEGMENT
   NESTED TABLE
   ROLLBACK
   TABLE
   TABLE PARTITION
   TYPE2 UNDO
   TYPE2 UNDO (ORA-1651)

<segment name> name is stated in the error message


3. Compute the NEXT EXTENT SIZE if the segment resides in a dictionary managed tablespace and has a PCT_INCREASE >0

SELECT EXTENT_MANAGEMENT FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = '<tablespace name>';

Use the "next_extent" size with "pct_increase" (from #2 above) in the following formula to determine the size of extent that is trying to be allocated.

extent size = next_extent * (1 + (pct_increase/100)

EXAMPLE

next_extent = 512000
pct_increase = 50

next extent size = 512000 * (1 + (50/100)) = 512000 * 1.5 = 768000

NOTES:

ORA-01650 Rollback Segment

     pct_increase is only needed for early versions of Oracle, by  default in later versions pct_increase for a rollback segment is 0.

ORA-01652 Temporary Segment

    Temporary segments take the default storage clause of the tablespace  in which they are created.

     If this error is caused by a query, then try and ensure that the query  is tuned to perform its sorts as efficiently as possible.

    To find the owner of a sort, please refer to Note 1069041.6.


4) Determine which solution best fits the conditions

     If the NEXT EXTENT size (step 2 or 3 above) is larger than the largest contiguous chunk of free space then 
         Manually Coalesce Adjacent Free Extents may be an option
         If after coalescing ... there is still insufficient contiguous space ... then one of the other options must be chosen

     If the volumes on which the datafile(s) for the tablespace have insufficient space then
         Add a Datafile or Defragment the Tablespace are your only options ... and this file must be added to a new volume with sufficient space

II. Possible Solutions

There are several options for resolving UNABLE TO EXTEND errors

A. Manually Coalesce Adjacent Free Extents

ALTER TABLESPACE <tablespace name> COALESCE;

The extents must be adjacent to each other for this to work.

B. Modify one or more datafiles in the tablespace to use AUTOEXTEND

ALTER DATABASE DATAFILE '<full path and name>' AUTOEXTEND ON MAXSIZE <integer> <k | m | g | t | p | e>;

NOTE: It is strongly recommended that MAXSIZE be specified to try to prevent the datafile from consuming all available space on the volume

C. Add a Datafile

ALTER TABLESPACE <tablespace name> ADD DATAFILE '<full path and file name>' SIZE <integer> <k | m | g | t | p | e>;

D. Lower "next_extent" and/or "pct_increase" size if segment is in a Dictionary Managed Tablespace

For non-temporary and non-partitioned segments:

ALTER <SEGMENT TYPE> <segment_name> STORAGE ( next <integer> <k | m | g | t | p | e> pctincrease <integer>);

For non-temporary and partitioned segments:

ALTER TABLE <table_name> MODIFY PARTITION <partition_name> STORAGE ( next <integer> <k | m | g | t | p | e> pctincrease <integer>);

For a temporary segment problem: 

ALTER TABLESPACE <tablespace name> DEFAULT STORAGE (initial <integer> <k | m | g | t | p | e> next <integer> <k | m | g | t | p | e> pctincrease <integer>);

E. Resize the Datafile

ALTER DATABASE DATAFILE '<full path and file name>' RESIZE <integer> <k | m | g | t | p | e>;

ORA-07445 opidsa

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.3 to 10.2.0.3
Information in this document applies to any platform.

Description

After having applied the 10.2.0.3 patch set on any platform, processes from user sessions can core dump (ORA-7445) in opidsa().
The problem is also known to affect 10.2.0.2, but only for Windows platforms when running with 10.2.0.2 Patch 6 upwards.

Likelihood of Occurrence

The problem will typically be seen after the database has been running for some time (weeks). 

Possible Symptoms

The core dump is shown in the alert.log as messages similar to:

ORA-07445: exception encountered: core dump [opidsa()+480] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []

or

ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_opidsa+360] [PC:0x2080540] [ADDR:0x0] [UNABLE_TO_READ] []

Looking at the call stack in the trace file shows:

...
----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)     
-------------------- -------- -------------------- ----------------------------
 ksedmp()+744         CALL     ksedst()             000000840 ? 1066C42AC ?
                                                   000000000 ? 1066C0DA0 ?
                                                   1066BFB08 ? 1066C0508 ?
 ssexhd()+1240        CALL     ksedmp()             000106400 ? 10652CE64 ?
                                                   10652C000 ? 00010652C ?
                                                   000106400 ? 10652CE64 ?
 sigacthandler()+44   PTR_CALL 0000000000000000     10652A000 ? 1066C7EF0 ?
                                                   106526E2C ? 00010652A ?
                                                   00000000B ? 000000067 ?
 opidsa()+480         PTR_CALL 0000000000000000     00000000B ? 1066C7EF0 ?
                                                   1066C7C10 ? 000000001 ?
                                                   000000000 ? 000010000 ?
 ...

The offset (480 in the example) may vary.

We may have different code paths leading to the opidsa() call, such as:
... opidsa opiodr ttcpip opitsk opiino opiodr opirip opidrv ...
... opidsa kpodny opikpr opiodr rpidrus skgmstack ...

Note that it is also possible for this issue to be seen as a dump in opidsc().

Workaround or Resolution

No real workaround exists for the problem, but flushing the shared pool after receiving the error may clear the situation to prevent further occurrences for a while. Restarting the instance will also clear the problem for a period. Implementing regular flushes of the shared pool can prevent the problem from occurring (this could eg. be executed via DBMS_JOB outside business hours to minimize the impact).

The problem is fixed in 11g via non-published bug:5648872 and the fix is included in 10.2.0.4.

Viewer application profile is not set

Symptoms

Create document via Launch Journal Wizard, R12, errors with 'Viewer application profile is not set'

The viewer is NULL in the contextual information

Expected Behavior
==============
Document is created without any issue, in R12 ADI can't be used.

Cause

Profile option 'GL : Default Desktop Viewer' is not set.

Solution

To implement the solution, please execute the following steps:

1. The value displayed in the viewer field, which is currently null, is the 'GL : Default Desktop Viewer' profile option value.

2. This is needed if you are launching the Journal wizard using the shortcut link. Please set this profile option value and try to launch the JW.

Value could be as an example Excel 2000

3. Logout of application in order for the profile option to take the effect.

SQLGL: GL_BUD_INTG is an invalid integrator key

Symptoms

The following error occurs while trying to create the budget worksheet to upload amounts using budget wizard:

SQLGL: GL_BUD_INTG is an invalid integrator key .

Changes

None

Cause

These are the functions that are required for the menu that is assigned to the responsibility from which the budget upload is done.

Function User function name

BNE_ADI_CREATE_DOCUMENT Desktop Integration - Create Document
BNE_CREATE_DOCUMENT Create Document .

Solution

1. Go to Sysadmin--Application--Function and check if these two functions are available or not.

In case they are not available please add these:

Function User function name

BNE_ADI_CREATE_DOCUMENT Desktop Integration - Create Document ,
BNE_CREATE_DOCUMENT Create Document .

2. Go to Sysadmin--Application--Menu

Query the menu GL_SUPERUSER (this is usually the default menu that is assigned with General Ledger responsibility) add the following two menu functions that have been defined in step 1 above, under the field "Function" :

Desktop Integration - Create Document
Create Document

Line Drilldown Button Disabled

Last week we found the Line Drilldown button on journal entry screen for all sub ledgers journals. I consulted the problem to Metalink SR. They told me to check the SLA: Disable Journal Import system profile option . It should be set to No.
I then checked the system profile and found it to be Yes. After set it to No the difference I got are:
1. Create accounting on sub ledgers can be automaticaly imported to GL and automaticaly posted.
2. Drilldown button enabled.
The prolem is who changed the profile option, Oracle said the default is No.

Oracle Application Diagnostic 12.0.6

When you upgrade E-business diagnostic from 12.0.4 to 12.0.6, you may encounter < tr displayed on diagnostic page. This is easy to recover. Just bounce your application tier, the problem will be gone.

Shopping at ShopWiki

ShopWiki is a good site to search products on online shops. If you like Wikipedia or other Wikis, you will like this. Like this ShopWiki’s team sport section, you will see list of available team sports. If you click one, you will see not only available products for that sport, but you will also see some knowledge about that sport, e.g. rules, how to play, what needed to play, etc. Also you will get informed about anything related to what you search. So when you are ready to play, you already have all you need.

The ShopWiki is a complete starting page for shopping. I think it is because they do not only show paying shops, but all shops available online.