Quantcast
Channel: Doyensys Allappsdba Blog..
Viewing all 1640 articles
Browse latest View live

Article 2

$
0
0
ORA-25152: TEMPFILE cannot be dropped at this time

 Received above error when executed the below statement:

SQL> alter database tempfile '/u01/app/temp01.dbf' drop including datafiles; 

CAUSE :
An attempt was made to drop a TEMPFILE being used by online users.

SOLUTION:

Step 1:  Find the sessions that are using the TEMPFILE:

SQL> select  a.inst_id,   b.tablespace,   b.segfile#,   b.segblk#,
 round ( ( ( b.blocks * p.VALUE ) / 1024 / 1024 ), 2 ) size_mb,   a.SID,   a.serial#,   a.username,   a.osuser,
  a.program,  a.status from  v$session    a,   v$sort_usage b,   v$process    c,  v$parameter  d, where
  b.segfile# = <file number of TEMPFILE SEGMENT>
and
   d.name = 'db_block_size'
and 
   a.saddr = b.session_addr
and 
   a.paddr = c.addr
order by 
   b.tablespace,   b.segfile#,   b.segblk#,   b.blocks;

Step 2:  Kill all sessions that are using the TEMPFILE

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;

-- If you have a huge list, you can write the execution syntax online, as part of the query:

SQL> set heading off

SQL> spool runme.sql

SQL> select 'alter system kill session '''||a.sid||','||a.serial#||''' immediate;'
from 
   v$session    a,
   v$sort_usage b,
   v$process    c,
   v$parameter  d
where 
   d.name = 'db_block_size'
and 
   a.saddr = b.session_addr
and 
   a.paddr = c.addr
and 
   b.tablespace='TEMP' <-- Your TEMP tablespace name here
order by 
   b.tablespace,
   b.segfile#,
   b.segblk#,
   b.blocks;

SQL> spool off;

SQL> @runme.sql

Step 3:  Re-attempt to drop the TEMPFILE.

SQL> alter database tempfile '/u01/app/temp01.dbf' drop including datafiles;

REFERENCE:

http://www.dba-oracle.com/t_ora_25152_tempfile_cannot_be_dropped.htm

Article 1

$
0
0
AdminServer Start Failed With oracle.security.jps.JpsException: JPS-00027: There was an internal error: java.sql.SQLException: ORA-01017: invalid username/password; logon denied Received above error when executed the below statement:

CAUSE :

RF enabled domain has dependency on database-based Oracle Platform Security repository OPSS schema.
AdminServer startup will fall if there is issue accessing the OPSS schema.

The JDBC configuration for the OPSS schema database access is in DOMAIN_HOME/config/jdbc/opss-datasource-jdbc.xml
...
Sample snippet of opss-datasource-jdbc.xml
<name>opss-data-source</name>
<jdbc-driver-params>
 <url>jdbc:oracle:thin:@server1.oracle.com:1521/DBMW</url>
 <driver-name>oracle.jdbc.OracleDriver</driver-name>
 <properties>
  <property>
  <name>user</name>
   <value>PROD_OPSS</value>
  </property>
 </properties>
 <password-encrypted>{AES}.....=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
 <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
  <jndi-name>jdbc/OpssDataSource</jndi-name>
  <global-transactions-protocol>None</global-transactions-protocol>
 </jdbc-data-source-params>
</jdbc-data-source>

SYMPTOMS:

Start Weblogic AdminServer failed with following error in AdminServer.log

####<May 11, 2017 9:01:55 AM EDT> <Critical> <WebLogicServer> <OAS12C> <AdminServer> <main> <<WLS Kernel>> <> <53e386ae-df5f-4f89-8098-d6bf07c74f4c-00000002> <1494507715080> <[severity-value: 4] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
oracle.security.jps.JpsException: JPS-00027: There was an internal error: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
at oracle.security.jps.internal.config.OpssCommonStartup.start(OpssCommonStartup.java:209)
at oracle.security.jps.wls.JpsWlsStartup.start(JpsWlsStartup.java:96)
at oracle.security.jps.JpsStartup.start(JpsStartup.java:215)
at oracle.security.jps.wls.JpsDefaultService.start(JpsDefaultService.java:74)
at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:76)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1262)
at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:332)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:374)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:228)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2072)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:88)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1213)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1144)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:643)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:397)
...
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
Caused by: oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-00027: There was an internal error: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.handleDatabaseException(JpsDBDataManager.java:2146)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.processJPAException(JpsDBDataManager.java:2629)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.existsTable(JpsDBDataManager.java:1677)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.isPrincipalAssigneeSplit(JpsDBDataManager.java:1612)
...
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.1.v20150916-55dc7c3): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
Error Code: 1017
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:326)
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:138)
at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.setOrDetectDatasource(DatabaseSessionImpl.java:207)
...
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.existsTable(JpsDBDataManager.java:1654)
... 44 more
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:391)
at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:1126)
at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:507)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:546)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:440)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:1025)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:682)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:793)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:614)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:98)
####<May 11, 2017 9:01:55 AM EDT> <Notice> <WebLogicServer> <OAS12C> <AdminServer> <main> <<WLS Kernel>> <> <53e386ae-df5f-4f89-8098-d6bf07c74f4c-00000002> <1494507715205> <[severity-value: 32] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000365> <Server state changed to FAILED.>
####<May 11, 2017 9:01:55 AM EDT> <Error> <WebLogicServer> <OAS12C> <AdminServer> <main> <<WLS Kernel>> <> <53e386ae-df5f-4f89-8098-d6bf07c74f4c-00000002> <1494507715205> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000383> <A critical service failed. The server will shut itself down.>
####<May 11, 2017 9:01:55 AM EDT> <Notice> <WebLogicServer> <OAS12C> <AdminServer> <main> <<WLS Kernel>> <> <53e386ae-df5f-4f89-8098-d6bf07c74f4c-00000002> <1494507715205> <[severity-value: 32] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
####<May 11, 2017 9:01:55 AM EDT> <Info> <WebLogicServer> <OAS12C> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <53e386ae-df5f-4f89-8098-d6bf07c74f4c-00000003> <1494507715205> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000236> <Stopping execute threads.>
####<May 11, 2017 9:01:55 AM EDT> <Info> <WebLogicServer> <OAS12C> <AdminServer> <main> <<WLS Kernel>> <> <53e386ae-df5f-4f89-8098-d6bf07c74f4c-00000002> <1494507715220> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000238> <Shutdown has completed.>

APPLIES TO:

Oracle WebLogic Server - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

SOLUTION:

Using RCU to recreate database users only will not work because the db users and db objects are configured during instance configuration and subsequent instance configuration/usage.  If the database is lost, the database users must be recreated again using RCU and run config to create the instance again.
1. Make sure all instance processes are stopped.

2. Rename DOMAIN_HOME directory eg. from base_domain to base_domain.old
    -The old domain directory can be deleted at a later time.

3. Make a copy of beahomelist
   Window: C:\bea\beahomelist
   Linux :    $HOME/bea/beahomelist

4. If domain entry exist in beahomelist, remove the entry

5. Run RCU to create the database users

6. Run config.sh to create the instance

REFERENCE:

Metalink Doc ID 2265421.1

Article 0

$
0
0
ORA-28014: Cannot Drop Administrative Users

CAUSE :

The user was created by a script executed via catcon.pl. The users created this way are considered administrative users since in that session the parameter "_oracle_script" is set to TRUE.

SYMPTOMS:

While trying to drop an user in a multitenant database the following error is seen: 

SQL> drop user jpop cascade;
drop user jpop cascade
*
ERROR at line 1:
ORA-28014: cannot drop administrative users

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.

SOLUTION:

Avoid creating users by running a script via catcon.pl. If the users must be dropped then drop them via catcon.pl as well or set "_oracle_script" to TRUE before dropping the users directly:

SQL> alter session set "_oracle_script"=true;
Session altered.

SQL> drop user gigi1 cascade;
User dropped.

REFERENCE:

Metalink Doc ID 1566042.1

Article 3

$
0
0

       PDF is not opening in oracle apex application


Error:

    
          While opening PDF in oracle apex application its opened as blank page.


solution:


         check in the  schema_properties.properties file for username and password for the particular schema if the password is not match please reset the password for the particular user as per the schema_properties.properties file.

Article 2

$
0
0
Error:

upload of Context file and templates to database...ERROR: InDbCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.upload_context_file(:1,:2,:3,:4,:5); END;: 1; Oracle error -4063: ORA-04063: package body "APPS.FND_GLOBAL" has errors has been detected in FND_GSM_UTIL.upload_context_file. 

SQL> alter package apps.FND_GLOBAL compile body; 

Warning: Package Body altered with compilation errors. 

SQL> show errors 
Errors for PACKAGE BODY APPS.FND_GLOBAL: 

LINE/COL ERROR 
-------- ----------------------------------------------------------------- 
2048/11 PL/SQL: SQL Statement ignored 
2050/18 PL/SQL: ORA-04063: view "APPS.FND_USER_RESP_GROUPS" has errors 
SQL> alter view APPS.FND_USER_RESP_GROUPS compile; 

Warning: View altered with compilation errors. 

SQL> 
SQL> 
SQL> show errors view APPS.FND_USER_RESP_GROUPS 
Errors for VIEW APPS.FND_USER_RESP_GROUPS: 

LINE/COL ERROR 
-------- ----------------------------------------------------------------- 
0/0 ORA-04063: view "APPS.WF_USER_ROLE_ASSIGNMENTS_V" has errors 
SQL> 
SQL> 
SQL> alter view APPS.WF_USER_ROLE_ASSIGNMENTS_V compile; 

Warning: View altered with compilation errors. 

SQL> show errors view APPS.WF_USER_ROLE_ASSIGNMENTS_V; 
Errors for VIEW APPS.WF_USER_ROLE_ASSIGNMENTS_V: 

LINE/COL ERROR 
-------- ----------------------------------------------------------------- 
0/0 ORA-00980: synonym translation is no longer valid 

Workaround:

1. Please run:

adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp APPLSYS apps APPS apps THIN \
test1.ro.oracle.com:1521:VIS TABLE \
$FND_TOP/patch/115/xdf/wf_local_user_roles.xdf $FND_TOP/patch/115/xdf/xsl changedb=y

2. Validate 'APPS.WF_USER_ROLES'

3. Please run:
adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp APPLSYS apps APPS apps THIN \
test1.ro.oracle.com:1521:VIS TABLE \
$FND_TOP/patch/115/xdf/wf_user_role_assignments.xdf $FND_TOP/patch/115/xdf/xsl changedb=y

4. Check if WF_USER_ROLE_ASSIGNMENTS_V is valid.

5. recompile WF_DIRECTORY

6. After that compile the package body also (FND_GLOBAL)

SQL> alter view apps.WF_USER_ROLE_ASSIGNMENTS_V compile; 

View altered. 

SQL> alter view APPS.FND_USER_RESP_GROUPS compile; 

View altered. 

SQL> select object_name,owner,object_type,status from dba_objects where object_name='WF_USER_ROLE_ASSIGNMENTS_V'; 

OBJECT_NAME 
-------------------------------------------------------------------------------- 
OWNER OBJECT_TYPE STATUS 
------------------------------ ------------------- ------- 
WF_USER_ROLE_ASSIGNMENTS_V 
APPS VIEW VALID 


SQL> select object_name,owner,object_type,status from dba_objects where object_name='WF_DIRECTORY'; 

OBJECT_NAME 
-------------------------------------------------------------------------------- 
OWNER OBJECT_TYPE STATUS 
------------------------------ ------------------- ------- 
WF_DIRECTORY 
APPS PACKAGE VALID 

WF_DIRECTORY 
APPS PACKAGE BODY INVALID 

---------------------------------------------------------------------------------------------------------------------------------------- 
OBJECT_NAME 
-------------------------------------------------------------------------------- 
OWNER OBJECT_TYPE STATUS 
------------------------------ ------------------- ------- 
WF_DIRECTORY 
APPS PACKAGE VALID 

WF_DIRECTORY 
APPS PACKAGE BODY VALID

7.  alter package apps.FND_GLOBAL compile body; 

Package body altered. 

Article 1

$
0
0

       HOW TO BACKUP ORACLE APEX APPLICATION                                      THROUGH BACK END


1) To use APEXExport, a JDK of version 1.5 or greater must be used.  Additionally, the Oracle JDBC
class libraries must be in your CLASSPATH.

To set the CLASSPATH, following are some examples:

export CLASSPATH=.:${ORACLE_HOME}/jdbc/lib/ojdbc5.jar

...from the Bash shell or ...

set CLASSPATH=%CLASSPATH%;.\;%ORACLE_HOME%\jdbc\lib\ojdbc5.jar

...from Windows environments.

2) From the apex/utilities directory, issue the command:

   java oracle.apex.APEXExport

java oracle.apex.APEXExport -db HOSTNAME:PORT:SID -user <USERNAME> -password <PASSWORD> -applicationid <ID>

Article 0

$
0
0

                   How to Apply Opatch on Oracle RAC instances



Steps:

       1) Check Oracle service status
               
                                       crs_stat -t


   2)Stop database instance one by one
 
                                      srvctl stop instance -i DB_NAME 1 -d INSTANCE_NAME 
                srvctl stop instance -i DB_NAME 2 -d INSTANCE_NAME

   3)Stop ASM instance on each node one by one

                                      srvctl stop asm -n rac-node1
                srvctl stop asm -n rac-node2

   4)Go to the downloaded patch folder 

                                      export OPATCH  path
 
               export PATH=$PATH:$ORACLE_HOME/Opatch                                

       5)Check whether patch is applied or not

                                       opatch lsinventry
                                
        6)Start apply patch

                               opatch apply                    
     

After applying opatch  successfully

        7)Restart the database instance and asm instance

                                       srvctl start asm -n rac-node1
                                       srvctl start asm -n rac-node2
                                       srvctl start instance -i DB_NAME 1 -d INSTANCE_NAME 
                                       srvctl start instance -i DB_NAME 2 -d INSTANCE_NAME


    8)Then take the invalid count on both nodes 
    






OPatch failed to locate Central Inventory/OPatch failed with error code 73

$
0
0
Solution:

The following problem was caused by our recent migration, the inventory was pointing to a home that was no longer on the server.

We need to attach the current home to the inventory, by using below command we can solve this issue.

$cd $OH/oui/bin

$ ./runInstaller -silent -invPtrLoc "/etc/oraInst.loc" -attachHome ORACLE_HOME="/u01/app/oracle/product/11.2.0.4" ORACLE_HOME_NAME="ORACLEHOME"
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB.   Actual 18432 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /u01/app/oracle/oraInventory

'AttachHome' was successful.

Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed.

$
0
0
Problem:
Opatch failed with following error message
Missing command :fuser
Prerequisite check "CheckSystemCommandAvailable" failed.

Solution:

Solution Description:
Go to patch home/bin directory. go to $ORACLE_HOME/bin and create a file with name fuser. This will solve your issue.
cd $GRID_HOME/bin
touch fuser
chmod 755 fuser
ls -tlr fuser
-rwxr-xr-x 1 dba oinstall 0 Aug 25 01:51 fuser

Re- run opatch session and check.

ORA-01516: nonexistent log file, data file, or temporary file

$
0
0
Issue:

SQL> alter database rename file '/u01/oradata/SAMPLE/index19.dbf'     to '/u06/oradata/SAMPLE/index19.dbf';
alter database rename file '/u01/oradata/SAMPLE/index19.dbf'     to '/u06/oradata/SAMPLE/index19.dbf'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01516: nonexistent log file, data file, or temporary file
"/u01/oradata/SAMPLE/index19.dbf"

Causes:-

1.This file is not available the mentioned location
2.check the name of the datafile(case sensitive)

Solution:-

1. Check the fild# and location from v$datafile and re run the query.

STANDBY- ORA-01275: Operation RENAME is not allowed if standby file management is automatic

$
0
0
Issue:-

While re-locating oracle datafile's below error we are getting.

SQL> alter database rename file '/u01/oradata/SAMPLE/data10.dbf' to '/u04/oradata/SAMPLE/data10.dbf';
alter database rename file '/u01/oradata/SAMPLE/data10.dbf' to '/u04/oradata/SAMPLE/data10.dbf'
*
ERROR at line 1:
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.

Cause:-

The standby file_management is set to auto on standby database.

Solution:

Run below command and try to re-run the query

alter system set standby_file_management=manual

once re-locating of datafile completed you can change back to "AUTO"

alter sytem set standby_file_management=auto

Article 0

$
0
0

                  During the R12.2 cloning process adcfgclone fails with error 

  Error:

                      Below Oracle Homes are already registered in the global inventory:
                      /u01/oracle/R122/fs1/FMW_Home/oracle_common
                      /u01/oracle/R122/fs1/FMW_Home/webtier
                      /u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1


 Cause:

                  The above Oracle Homes are unregistered from the global inventory


 Solution:

             Make sure that the above Oracle Homes are unregistered from the global inventory. we                         should always clean the oraInventory directory by using the following commands.

             cd $ORACLE_HOME/oui/bin
 
              ./runInstaller -silent -deinstall REMOVE_HOMES=                                 {“/u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1”}
              ./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/oracle_common”}
              ./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/webtier”}
   

                                        Then restart the adcfgclone.pl appsTier




11i reports going in to error

$
0
0
11i instance concurrent requests going in to error due to oracle tool kit error. 


Error
-------




Solution
----------

1.Set the display properly.
2.Login as the oracle user and set the env and type vncserver

Unable to open the log file and output file in oracle apps 11i

$
0
0
Error:
-------

11i error- An error occurred while attempting to receive the output arguments of the remote procedure. Function ncrorou returned error code 3010. The Applications File Server proces


Solution
-----------

Step 1:

Check for the space in mount point

Step 2:

  Clear unnecessary files from the mount point

Step 3:

    Clear the space in tmp directory

Reproduce the issue

Change oc4j administrator password

$
0
0
Step to change oc4j admin password manually:
---------------------------------------------------------

Step 1:
--------
Stop OC4J and the Application Server Control.

Enter the following command in the Oracle home of the application server instance:

(UNIX) ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J
(Windows) ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=OC4J

Step 2:
---------

Locate and open the following file in a text editor:

(UNIX)ORACLE_HOME/j2ee/home/config/system-jazn-data.xml
(Windows)ORACLE_HOME\j2ee\home\config\system-jazn-data.xml

Step 3:
---------
Locate the line that defines the credentials property for the oc4jadmin user.

The following example shows the section of system-jazn-data.xml with the encrypted credentials entry in boldface type:



    jazn.com
   
     .
     .
     .
     
          oc4jadmin
          OC4J Administrator
          OC4J Administrator
            {903}4L50lHJWIFGwLgHXTub7eYK9e0AnWLUH
     
Step 4:
---------

Replace the existing encrypted password with the new password.

Be sure to prefix the password with an exclamation point (!). For example:

!mynewpassword123

The password for the oc4jadmin user should conform to following guidelines:

Must contain at least five characters, but not more than 30 characters.

Must begin with an alphabetic character. It cannot begin with a number, the underscore (_), the dollar sign ($), or the number sign (#).

At least one of the characters must be a number.

Can contain only the following characters; numbers, letters, and the following special characters: US dollar sign ($), number sign (#), or underscore (_).

Cannot contain any Oracle reserved words, such as VARCHAR.

Step 5:
---------
Delete cached password data by deleting the contents of the following directory:

(UNIX)
ORACLE_HOME/j2ee/oc4jinstance /persistence/ascontrol/ascontrol/securestore/
(Windows)
ORACLE_HOME\j2ee\oc4jinstance\persistence\ascontrol\ascontrol\securestore/

Start OC4J and the Application Server Control.

Step 6:
----------
After the restart, the Application Server Control will use your new Administrator (oc4jadmin) password, which will be stored in encrypted format within the system-jazn-data.xml file.

Autoadjustments Errors with Frm-40735, ORA-04062: signature of package.

$
0
0

Autoadjustments fails with


FRM-40735: PRE-COMMIT trigger raised unhandled exception ORA-04062.
ORA-04062: signature of package "APPS.FND_REQUEST" has been changed

CAUSE

Library files need to be recompiled

The form ARXSUBAA was compiled successfully, however it is the library that is calling fnd_request(ARXSUBAA.pld)


SOLUTION

First, compile the library which is calling fnd_request - ARXSUBAA.pld
Then Compile the form - ARXSUBAA.fmb

Rerun the autoadjustments.

adformsctl.sh: exiting with status 150

$
0
0


If adoacorectl.sh,adformsctl.sh,adoafmctl.sh not coming up after start the application services
adoacorectl.sh: exiting with status 150
adformsctl.sh: exiting with status 150
adoafmctl.sh: exiting with status 150

Check the log file for these three processes:
$LOG_HOME/appl/admin/log/adoacorectl.txt
$LOG_HOME/appl/admin/log/adoafmctl.txt 
$LOG_HOME/appl/admin/log/adoaformsctl.txt 
If you see error like below

"opmn id=app01.rajeev01.com:6200
    no processes or applications matched this request

adoafmctl.sh: exiting with status 150"



Stop all three services. 
Clean the directory, under  persistence from below directory and restart all three services
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence
$ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence
$ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence

ORA-20100: Error: FND_FILE failure. Unable to create file in the directory

$
0
0



Problem details:
The Concurrent program is getting completed successfully, able to view output & logfile. But in the log file, it shows below error.
Oracle error 20100: java.sql.SQLException: ORA-20100: Error: FND_FILE failure. Unable to create file, o0165247.tmp in the directory, /testebs1/applcsf/tmp.
You will find more information in the request log.
ORA-06512: at "APPS.FND_FILE", line 417
ORA-06512: at "APPS.FND_FILE", line 526
ORA-06512: at "APPS.FND_CONCURRENT", line 1335
ORA-06512: at line 1
has been detected in FND_CONCURRENT.SET_INTERIM_STATUS.Successfully resubmitted concurrent program FNDOAMCOL with request ID 8907654 to start at 25-JAN-2017 22:38:56 (ROUTINE=AFPSRS)

Resolution:
Step 1: Stop the application.
Step 2: Manually delete the files under $APPLCSF/$APPLLOG
Step 3: Restart the application and retest the issue.


Creating the Autoconfig Script in DBTier

$
0
0
Steps:
      1. Creating the Context file
      2. Creating the autoconfig script folder in DBTier
      3.Executing the autoconfig file.


1) Creating the Context file:

[oracle@myebs bin]$ perl adbldxml.pl appsuser=apps appspasswd=apps jtop=/u01/mydb/db/tech_st/11.1.0/appsutil_bkp/jre

Starting context file generation for db tier..
Using JVM from /u01/mydb/db/tech_st/11.1.0/appsutil_bkp/jre/bin/java to execute java programs..

The log file for this adbldxml session is located at:
/u01/mydb/db/tech_st/11.1.0/appsutil/log/adbldxml_10110135.log

Enter the value for Display Variable:

Invalid input, reenter the value for Display Variable: 2

The context file has been created at:
/u01/mydb/db/tech_st/11.1.0/appsutil/PROD_myebs.xml
[oracle@myebs bin]$ cd /u01/mydb/db/tech_st/11.1.0/appsutil/
[oracle@myebs appsutil]$ ls
bin  html  java  log  media  perl  PROD_myebs.xml  sql  template
[oracle@myebs appsutil]$ cd bin/

2) Creating the Autoconfig Script folder in DBTier:

[oracle@myebs bin]$ sh adconfig.sh contextfile=/u01/mydb/db/tech_st/11.1.0/appsutil/PROD_myebs.xml appspass=apps

The log file for this session is located at: /u01/mydb/db/tech_st/11.1.0/appsutil/log/PROD_myebs/10110138/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.
        Using ORACLE_HOME location : /u01/mydb/db/tech_st/11.1.0
        Classpath                   : :/u01/mydb/db/tech_st/11.1.0/jdbc/lib/ojdbc6.jar:/u01/mydb/db/tech_st/11.1.0/appsutil/java/xmlparserv2.jar:/u01/mydb/db/tech_st/11.1.0/appsutil/java:/u01/mydb/db/tech_st/11.1.0/jlib/netcfg.jar:/u01/mydb/db/tech_st/11.1.0/jlib/ldapjclnt11.jar

        Using Context file          : /u01/mydb/db/tech_st/11.1.0/appsutil/PROD_myebs.xml

Context Value Management will now update the Context file

        Updating Context file...COMPLETED

        Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db111
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

[oracle@myebs PROD_myebs]$ pwd
/u01/mydb/db/tech_st/11.1.0/appsutil/scripts/PROD_myebs
[oracle@myebs PROD_myebs]$ ls -ltr
total 60
-rw------- 1 oracle oinstall  1303 Oct 11 01:40 adstrtdb.sql
-rw------- 1 oracle oinstall   805 Oct 11 01:40 adstopdb.sql
-rwx------ 1 oracle oinstall  7384 Oct 11 01:40 adexecsql.pl
-rwx------ 1 oracle oinstall  5274 Oct 11 01:40 adchknls.pl
-rwx------ 1 oracle oinstall 15247 Oct 11 01:40 adpreclone.pl
-rwx------ 1 oracle oinstall  3450 Oct 11 01:40 adlsnodes.sh
-rwx------ 1 oracle oinstall  6749 Oct 11 01:40 addlnctl.sh
-rwx------ 1 oracle oinstall  2760 Oct 11 01:40 addbctl.sh
-rwx------ 1 oracle oinstall  1518 Oct 11 01:40 adautocfg.sh
[oracle@myebs PROD_myebs]$

3) Executing the Auto Config:

[oracle@myebs PROD_myebs]$ sh adautocfg.sh
Enter the APPS user password:
The log file for this session is located at: /u01/mydb/db/tech_st/11.1.0/appsutil/log/PROD_myebs/10110140/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.
        Using ORACLE_HOME location : /u01/mydb/db/tech_st/11.1.0
        Classpath                   : :/u01/mydb/db/tech_st/11.1.0/jdbc/lib/ojdbc6.jar:/u01/mydb/db/tech_st/11.1.0/appsutil/java/xmlparserv2.jar:/u01/mydb/db/tech_st/11.1.0/appsutil/java:/u01/mydb/db/tech_st/11.1.0/jlib/netcfg.jar:/u01/mydb/db/tech_st/11.1.0/jlib/ldapjclnt11.jar

        Using Context file          : /u01/mydb/db/tech_st/11.1.0/appsutil/PROD_myebs.xml

Context Value Management will now update the Context file

        Updating Context file...COMPLETED

        Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db111
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

[oracle@myebs PROD_myebs]$

Steps for Database Failover

$
0
0

Steps for Database Failover




Check the archive log sync gap in DR if we found gap we need to sync. Check the gap by using bellow query .


1. select name,open_mode from v$database;

2. select name,open_mode,database_role from v$database;

3.SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE#"Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
FROM
(SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
WHERE
ARCH.THREAD# = APPL.THREAD#




4. ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;


5. select name,open_mode,database_role from v$database;

6. ALTER DATABASE ACTIVATE STANDBY DATABASE;

7. select name,open_mode,database_role from v$database;


8. alter database open;
9. select name,open_mode,database_role from v$database;

10.Shut immediate;

11. Startup;



 

Viewing all 1640 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>