Technical troubleshooting and more

I faced this error while trying to restore & recover of a PDB (pluggable database) part of the log file and the solution is described here below: log: initialization parameters used for automatic instance: db_name=CDB db_unique_name=gbux_pitr_PDB1_CDB compatible=12.1.0.2.0 db_block_size=8192 db_files=200 diagnostic_dest=/oracle/app/oracle _system_trig_enabled=FALSE sga_target=1888M processes=200 db_create_file_dest=/oracle/auxilary log_archive_dest_1='location=/oracle/auxilary' enable_pluggable_database=true _clone_one_pdb_recovery=true #No auxiliary parameter file used starting up automatic instance CDB RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 07/31/2016 16:22:20 RMAN-04014: startup failed: ORA-27104: system-defined limits for shared

In order to make a recovery catalog using a pluggable database as part of your container database you should follow these instructions special notes * PDB can act as a recovery catalog * Recovery catalog is not supported when connected to pluggable database * You must register the whole CDB agains the PDB catalog Creating pluggable database for RMAN catalog bash-4.2$ echo $ORACLE_SID CDB bash-4.2$ sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu Jul 28 15:38:17 2016 Copyright (c) 1982, 2014, Oracle.  All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options SQL> create pluggable database rman admin user rman identified by rman; SQL> alter session set container = rman; Session altered. SQL> alter database open; Database altered. Preparing specific tablespace  SQL> conn sys@RMAN as sysdba

When trying to apply patch you may face this error the solution is described below. ERROR: bash-4.2$ ../opatch apply Oracle Interim Patch Installer version 12.2.0.1.5 Copyright (c) 2016, Oracle Corporation.  All rights reserved. Oracle Home       : /oracle/app/oracle/product/12.1.0 Central Inventory : /oracle/app/oracle/oraInventory    from           : /oracle/app/oracle/product/12.1.0/oraInst.loc OPatch version    : 12.2.0.1.5 OUI version       : 12.1.0.2.0 Log file location : /oracle/app/oracle/product/12.1.0/cfgtoollogs/opatch/opatch2016-07-27_16-27-44PM_1.log Verifying environment and performing prerequisite checks... Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite check &qu

in order to use PuTTY with X11 FW feature you will need to follow these instructions: 1. in PuTTY configuration -> go to Connection settings -> SSH -> X11     check the Enable X11 forwarding 2. check /etc/ssh/sshd_config  that X11 forwarfing flag set to yes     if not - change to yes and restart sshd service [root]# service sshd restart 3. open your server terminal using putty 4. check DISPLAY parameter by typing  ##echo $DISPLAY     you should get:  localhost:10.0 (or something similar) 5. open Xming on your local machine (your PC) 6. type xclock command and you should see it common problems that you can face during your xclock configuration experience and solutions: if xclock is not found in your Linux server -> install xorgs-X11-apps rpm: [root]#  yum install xorg-x11-apps xclock command gives Can't open display output [root]# xclock

There are few reasons that make your indexes become unusable 1. the unusable command statement  - ALTER INDEX idx UNUSABLE; 2. direct path writes to the index's table - such as using sqlldr utility using direct=y flag     In this case you can create multiple PK values and until you will clear the duplication the PK will be in unusable state.     * using /+ APPEND +/ hint behaves differently from sqlldr.      Although it's direct path as well Oracle will give unique constraints errors. 3. reorganizing table extents by using move command - ALTER TABLE tbl MOVE; take these operations in your consideration when developing your application since you will need to spend some time and resources in order to fix the indexes (rebuild for example) during your process. I'm not saying direct path is bad, just be aware of the consequences. :-) Good Luck,

Hi there Backup up Jenkins configuration is very simple as you will see right now. under your $JENKINS_HOME you have several important folders. (Assuming your Jenkins installed from RPM your JENKINS_HOME=/var/lib/jenkins) one of these folders is jobs if you need to backup only the configuration of your jobs without any other information such as previous builds and artifacts you can backup only config.xml file per each job. in case you have special plugins it's better for you to backup $JENKINS_HOME/plugins folder as well. custom nodes information can be found here : $JENKINS_HOME/nodes these are necessary for manual backup strategy. in case you will need to restore Jenkins you will need to install Jenkins from scratch and extract the backed up files under the correct folder structure. better way is to look for backup plugin to integrate from your Jenkins console. for example: https://wiki.jenkins-ci.org/display/JENKINS/Backup+Plugin enjoy

After deleteing rows from a table with LOB column you will still see same number of extents and size capacity. in order to claim back the space of the LOB SEGMENT you will need to run this command: ALTER TABLE your_table MODIFY LOB (your lob column) (SHRINK SPACE); validation of reclaiming the space- Identify the segment name using this query: select * from DBA_LOBS where TABLE_NAME = 'your table' and COLUMN_NAME = 'your column'; Validate the size reduction by quering DBA_EXTENTS table where SEGMENT_NAME is the SEGMENT_NAME from above query. Good luck

Hi assuming you have installed correctly these components: ORACLE DB (including instance and listener) ODBC driver and you are facing this problem: [root@linuxRHEL6 bin]# isql -v simple [01000][unixODBC][Driver Manager]Can't open lib '/usr/lib/oracle/11.2/ client64/lib/libsqora.so.11.1' : file not found   you should check the following [root@linuxRHEL6 bin]# ldd /usr/lib/oracle/11.2/client64/ lib/libsqora.so.11.1 ldd: warning: you do not have execution permission for `/usr/lib/oracle/11.2/ client64/lib/libsqora.so.11.1'         linux-vdso.so.1 =>  (0x00007fffa11d1000)         libdl.so.2 => /lib64/libdl.so.2 (0x00007f5c2585e000)         libm.so.6 => /lib64/libm.so.6 (0x00007f5c255d9000)         libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5c253bc000)         libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f5c251a3000)         libclntsh.so.11.1 => /usr/lib/oracle/11.2/client64/ lib/libclntsh.so.11.1 (0x00007f5c2283300