Skip to main content

Posts

Installing Oracle Enterprise Manager Cloud Control 13c Release 5 (13.5.0.0.0) for Linux x86-64

 Installing Oracle Enterprise Manager Cloud Control 13c Release 5 (13.5.0.0.0) for Linux x86-64 In this note, we will install the Oracle Enterprise Manager Cloud Control 13c Release 5 (13.5.0.0.0) for Linux x86-64 1. Download the software from the oracle support link  https://www.oracle.com/enterprise-manager/downloads/linux-x86-64-13c-rel5-downloads.html 2. Launch the installer after giving execute permission chmod +x em13500_linux64.bin [oracle@oel76 oem]$ ./em13500_linux64.bin ERROR: Temporary directory /tmp does not have enough free space. At least 12289 MB of free space are required. Please input another directory or [Exit]: /u01/oem/tmp Launcher log file is /u01/oem/tmp/OraInstall2025-12-16_06-44-55PM/launcher2025-12-16_06-44-55PM.log. Extracting the installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Recent posts

How to validate the system and EBS_SYSTEM passwords in EBS 12.2

 How to validate the system and EBS_SYSTEM passwords in EBS 12.2 In EBS 12.2. while using ad utilities esp adop to patch the applications, we may face the issue with system and EBS_SYSTEM passwords.  They should be same in EBS 12.2.  To validate these two passwords use the utility adValidateEbssystemSchema.pl applprod@server01:/u03/applsmu3/R122/fs1/EBSapps/appl/ad/12.0.0/bin$ perl adValidateEbssystemSchema.pl Enter the APPS password: Enter the SYSTEM password: Validating APPS credentials...validated successfully Validating SYSTEM credentials...validated successfully Validating EBS_SYSTEM user ebssys codelevel = C.0 ***** E R R O R ***** User : EBS_SYSTEM ORA-01017: invalid username/password; logon denied ********************* Error: EBS_SYSTEM password is not the same as SYSTEM password Please change the EBS_SYSTEM password to be the same as SYSTEM password ALTER USER EBS_SYSTEM IDENTIFIED BY <SYSTEM PASSWORD> applprod@server01: ------------------------------------...

XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator.

  XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator. Issue : When user logs into EBS, he gets the following Error :  xx_XXXXX  is not a valid responsibility for the current user. Please contact your System Administrator. Solution: 1. Check if the responsibility is end dated.  Extend the end-date if required and try to login again.  2. Check the profile option  Applications Start Page for the user ( User Level). If there is any value defined, remove it and save it. Try to login again and it worked in our case.  Before: After:

Add disk in virtual box vm

 Add disk in virtual box vm  In this post, we will check how to add disks in Virtual Box VM.  1. First add the disk from VM console as a new HDD as shown below: We have recently added oel76_db1.vdi disk. 2. Once the disk is added, it will be visible in fdisk -l command output.  3. create the partion using below command fdisk /dev/sdb  for new partion : type n,  to list partition : type p to write the partion : type w 4. Format the partition by below command: Now format the disk with  mkfs  command. # mkfs.ext4 /dev/sdb1 [root@oel76 etc]# mkfs.ext4 /dev/sdb1 mke2fs 1.42.9 (28-Dec-2013) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 15032320 inodes, 60108800 blocks 3005440 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=2208301056 1835 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backu...

Exception in thread "main" java.lang.UnsatisfiedLinkError: /u01/soft/ebs/startCD/Disk1/rapidwiz/jre/Linux_x64/1.6.0/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory

Error while launching rapidwiz during EBS 12.2 Installation  Exception in thread "main" java.lang.UnsatisfiedLinkError: /u01/soft/ebs/startCD/Disk1/rapidwiz/jre/Linux_x64/1.6.0/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory [oracle@oel76 rapidwiz]$ Exception in thread "main" java.lang.UnsatisfiedLinkError: /u01/soft/ebs/startCD/Disk1/rapidwiz/jre/Linux_x64/1.6.0/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory         at java.lang.ClassLoader$NativeLibrary.load(Native Method)         at java.lang.ClassLoader.loadLibrary0(Unknown Source)         at java.lang.ClassLoader.loadLibrary(Unknown Source)         at java.lang.Runtime.load0(Unknown Source)         at java.lang.System.load(Unknown Source)         at java.lang.ClassLoader$NativeLibrary.load(Native Method) ...

/lib/ld-linux.so.2: bad ELF interpreter: No such file or directory - while building stage during 12.2

 /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory Cause The Linux box is on a 64-bit system, and does not have 32-bit library support installed. Resolution Make sure glibc.i686 and glibc.x86_64 is installed on the system. If glibc.i686 is not available on the Centos-6, try glibc.i386 To list all the package with prefix "glibc" Run: yum list glibc. To install the package: Run sudo yum install glibc.i686 or sudo yum install glibc.i386 If you do not have sudo setup in the environment, type "su" to accquire superuser authority first. Then run: yum install glibc.i686

ORA-12777: A non-continuable error encountered.

 ORA-12777: A non-continuable error encountered.  Check the error stack for additional information [ksm_check_ob_paths:1], [ORACLE_BASE], [], []. After moving the 19c Database Oracle Home to new location, i relinked the binaries and then tried to start up the database.  Got the below error: ORA-12777: A non-continuable error encountered.  Check the error stack for additional information [ksm_check_ob_paths:1], [ORACLE_BASE], [], []. Solution: Correct the path of Oracle Home in the  orabasetab file under $ORACLE_HOME/Install location e.g  oraprod@erpdbpreprod1:/u01/app/oracle/product/19.0.0/dbhome_3/install$ cat orabasetab #orabasetab file is used to track Oracle Home associated with Oracle Base /u01/app/oracle/product/19.0.0/dbhome_3:/u01/app/oracle/product/19.0.0:SPROD_DB__u01_app_oracle_product_19_0_0_dbhome_3:N: Note: dbhome_1 was corrected to dbhome_3 

19c RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

 19c RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Before doing an RMAN DUPLICATE DATABASE from an Active Database, we need to set up listener on the target environment with static registration.  Else when the RMAN shuts down the auxiliary database for creating spfile or making changes in it, it will not be able to connect the auxiliary and start the database (nomount) and throw the error : RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor To Solve this issue ensure that listener is configured with static registration using the below syntax : ========= LISTENER.ORA================== EBSUPG =   (DESCRIPTION_LIST =     (DESCRIPTION =       (ADDRESS = (PROTOCOL = TCP)(HOST =<hostname>)(PORT = 1536))       (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1536))   ...

ORA-01111: name for data file 975 is unknown - rename to correct file MRP0: Background Media Recovery terminated with error 1111

 ORA-01111: name for data file 975 is unknown - rename to correct file  MRP0: Background Media Recovery terminated with error 1111 Issue:  Standby database throws below errors and stops the MRP.  MRP0: Background Media Recovery terminated with error 1111 Errors in file /u01/app/oraprod/diag/diag/rdbms/sprod/SPROD1/trace/SPROD1_pr00_23061.trc: ORA-01111: name for data file 975 is unknown - rename to correct file ORA-01110: data file 975: '/u01/app/oraprod/11.2.0.4/dbs/UNNAMED00975' ORA-01157: cannot identify/lock data file 975 - see DBWR trace file ORA-01111: name for data file 975 is unknown - rename to correct file ORA-01110: data file 975: '/u01/app/oraprod/11.2.0.4/dbs/UNNAMED00975' Recovery Slave PR00 previously exited with exception 1111 Solution: - Please cancel the managed recovery by SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; - Set standby_file_management=manual SQL>ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL; If the physical standb...

Fatal Error: TXK Install Service RW-50010: Error: - script has returned an error: /bin/sh: error importing function definition for `which'

Fatal Error: TXK Install Service   RW-50010: Error: - script has returned an error:  /bin/sh: error importing function definition for `which' Description: R12.2 Installation fails during Install web Tier.  ------------------------------------------------------ Fatal Error: TXK Install Service oracle.apps.fnd.txk.config.ProcessStateException: OUI process failed : Exit=1 See log for details. CMD= /u01/soft/ebs/TechInstallMedia/ohs11119/Disk1/runInstaller -waitForCompletion -ignoreSysPrereqs -force -silent  -responseFile /u01/oracle/tstebs/fs2/inst/apps/tstebs_ebs22/temp/cfgHome/response/APPS_OHS_HOME/txkOHS_11119.rsp     at oracle.apps.fnd.txk.config.OUIPatchActionNode.processState(OUIPatchActionNode.java:159)     at oracle.apps.fnd.txk.config.PatchActionNode.processState(PatchActionNode.java:187)     at oracle.apps.fnd.txk.config.PatchNode.processState(PatchNode.java:338)     at oracle.apps.fnd.txk.config.PatchesNode.proces...