Posts

Showing posts from 2016

Concurrent request shows Inactive phase with No-Manager status

A concurrent request has a life cycle consisting of the following phases: Pending, Running, and Completed. During each phase, a request has a specific status. Listed below are the possible statuses for each phase: Pending Phase - Normal, Standby, Scheduled, Waiting Running Phase - Normal, Paused, Resuming, Terminating Completed Phase - Normal, Error, Warning, Cancelled, Terminated Inactive Phase - Disabled, On Hold, No Manager If a concurrent request is on hold or unable to run when there are no active manager processes that can run the request, the request is placed in an Inactive phase. Review the following points when the concurrent request is in Inactive phase with No Manager status. 1. Verify that Internal Concurrent Manager(ICM) is up and running. Use any one navigation mentioned below to check the status details of Internal Manager. i) Oracle Applications Manager(OAM) > Site Map > Monitoring > Availability > Internal Concurrent Manager > View Status. ...

Oracle Apps R12 Custom Top Creation

login as: root Access denied root@172.19.0.26's password: Last login: Wed Jul 24 11:23:17 2013 from 172.19.0.77 1) Make the directory structure for your custom application files. [root@server2 ~]# su - applvr12 [applvr12@server2 ~]$ mkdir XXUL [applvr12@server2 ~]$ cd $APPL_TOP [applvr12@server2 appl]$ mkdir xxul [applvr12@server2 appl]$ mkdir xxul/12.0.0 [applvr12@server2 appl]$ mkdir xxul/12.0.0/admin [applvr12@server2 appl]$ mkdir xxul/12.0.0/admin/sql [applvr12@server2 appl]$ mkdir xxul/12.0.0/admin/odf [applvr12@server2 appl]$ mkdir xxul/12.0.0/sql [applvr12@server2 appl]$ mkdir xxul/12.0.0/bin [applvr12@server2 appl]$ mkdir xxul/12.0.0/reports [applvr12@server2 appl]$ mkdir xxul/12.0.0/reports/US [applvr12@server2 appl]$ mkdir xxul/12.0.0/forms [applvr12@server2 appl]$ mkdir xxul/12.0.0/forms/US [applvr12@server2 appl]$ mkdir xxul/12.0.0/lib [applvr12@server2 appl]$ mkdir xxul/12.0.0/out [applvr12@server2 appl]$ mkdir xxul/12....

ORA-01157

ORA-01157: cannot identify/lock data file 6 - see DBWR trace file ORA-01110: data file 1: '/PRIM/u02/oradata/orcl/users01.dbf' SQL> startup ORACLE instance started. Total System Global Area 1286066176 bytes Fixed Size                                2287960 bytes Variable Size                        452986536 bytes Database Buffers               822083584 bytes Redo Buffers                         8708096 bytes Database mounted. ORA-01157: cannot identify/lock data file 6 - see DBWR trace file ORA-01110: data file 1: '/PRIM/u02...

ORA-01113

ORA-01113: file 1 needs media recovery ORA-01110: data file 1: '/oradata/orcl/system01.dbf' cause : An attempt was made to online or open a database with a file that is in need of media recovery. Solution : First apply media recovery to the file and then open the database. Resolution: 1) Start the DB with mount option. SQL> startup mount ORACLE instance started. Total System Global Area 1603411968 bytes Fixed Size                                2288872 bytes Variable Size                      1040188184 bytes Database Buffers               553648128 bytes Redo Buffers          ...

bash profile and listener.ora file entries

After we've Installed a new database, we need to add entries in .bash_profile and listener.ora files as per our requirements. So here in this post I've shared the generally used entries. Add the below entries apart from already existing entries of your database. .bash_profile entry LD_LIBRABRY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRABRY_PATH CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH BASE_PATH=/usr/sbin:$PATH:$HOME/bin; export BASE_PATH PATH=$ORACLE_HOME/bin:$BASE_PATH; export PATH                                    listener.ora file entry SID_LIST_ocl =  (SID_LIST =   (SID_DESC =    (ORACLE_HOME=/u01/app/oraprim/product/12.1.0/dbhome_1)    (SID_NAME=orcl)   )  )

Check if the DISPLAY variable is set in Linux environment

Image
Most of the users have been getting Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set in Linux environment while checking requirement the oracle installations on  Linux 5.2 or later versions. Below is the screenshot of the issue I have tried plenty of options, even ignoring the pre-requisites. Finally, i have fixed this issue through one Linux command Steps to resolve this issue: 1) login into root user( su -l root) 2) execute this command xhost +SI:localuser:oracle 3) login to the oracle user 4) execute ./runInstaller Now, it'll work fine.

Batchloader issue in oracle webcenter content

I am using Oracle webcenter content 11.1.1.7.0. To configure a JDBC Driver for standalone applications i ran DomainHome/ucm/cs/bin/SystemProperties and entered the details as follows database driver classpath : /Integration/d02/app/oramdev/product/11.2.0/dbhome_1/jdbc/lib/ojdbc6.jar jdbc driver name : oracle.jdbc.OracleDriver jdbc connection string : jdbc:oracle:thin:@server2.yantro.com:1521/orcl.yantro.com jdbc username : DEV_OCS jdbc user password : schema password then i ran ./BatchLoader and it throws the following error. oramdev@server2 bin]$ ./BatchLoader 'DynamicConverter' component, version '2013_01_16 (rev 23669) 11.1.7.6', require s a missing feature. The feature 'ContentAccess' is not installed. >componentloader/4 06.21 19:11:19.106 main !csComponentRequiresMiss ingFeatures,DynamicConverter,2013_01_16 (rev 23669) 11.1.7.6,!syFeatureNotInstal led\,ContentAccess\,\,0 >(internal)/3 06.21 19:11:31.953 main !$Unable to start the batch...

RMAN: CONTROL FILE RECOVERY SCENARIOS

Every Oracle Database has a control file as one of its important file. It is a small binary file that records the physical structure of the database. The control file includes: – Database name – Names and locations of associated datafiles and redo log files – The timestamp of the database creation – The current log sequence number – Checkpoint information Without the control file, the database cannot be mounted and recovery is difficult. The control file must be available for writing by the Oracle Database server whenever the database is open. By default, at least one copy of the control file is created during database creation. On some operating systems the default is to create multiple copies. You should create two or more copies of the control file during database creation. You can also create control files later, if you lose control files or want to change particular settings in the control files. Remember that anytime you restore a control file from a backup, you...