Relocate datafiles for physical dataguard (Oracle 10.2)

Relocate datafiles for physical dataguard (Oracle 10.2)

We will relocate the following files at a physical data guard situation.

File Move file to
/u02/oradata/HRPRD/hrapp.dbf /u07
/u03/oradata/HRPRD/psundo03.dbf /u06
/u05/oradata/HRPRD/psindex04.dbf /u04

hrapp.dbf and psindex04.dbf are regular data files. Since psundo03.dbf is a data file in undo table space, it takes more steps.

1. Rename files at primary

SQL> col file_name format a40
SQL> select file_name, tablespace_name from dba_data_files where file_name like '%hrapp.dbf';

FILE_NAME TABLESPACE_NAME
---------------------------------------- ------------------------------
/u02/oradata/HRPRD/hrapp.dbf HRAPP

SQL> select file_name, tablespace_name from dba_data_files where file_name like '%psundo03.dbf';

FILE_NAME TABLESPACE_NAME
---------------------------------------- ------------------------------
/u03/oradata/HRPRD/psundo03.dbf PSUNDO

SQL> select file_name, tablespace_name from dba_data_files where file_name like '%psindex04.dbf';

FILE_NAME TABLESPACE_NAME
---------------------------------------- ------------------------------
/u05/oradata/HRPRD/psindex04.dbf PSINDEX

SQL> alter tablespace HRAPP offline;

Tablespace altered.

SQL> !mv /u02/oradata/HRPRD/hrapp.dbf /u07/oradata/HRPRD/hrapp.dbf

SQL> alter tablespace HRAPP rename datafile '/u02/oradata/HRPRD/hrapp.dbf' to '/u07/oradata/HRPRD/hrapp.dbf';

Tablespace altered.

SQL> alter tablespace HRAPP online;

Tablespace altered.

2. Connect to standby database

SQL> alter database recover managed standby database cancel;

Database altered.

SQL> shutdown;
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL> ho
$ mv /u02/oradata/HRPRD/hrapp.dbf /u07/oradata/HRPRD/hrapp.dbf
$ exit

SQL> startup mount;
ORACLE instance started.

Total System Global Area 570425344 bytes
Fixed Size 2072872 bytes
Variable Size 293605080 bytes
Database Buffers 268435456 bytes
Redo Buffers 6311936 bytes
Database mounted.

SQL> alter system set standby_file_management=MANUAL;

System altered.

SQL> alter database rename file '/u02/oradata/HRPRD/hrapp.dbf' to '/u07/oradata/HRPRD/hrapp.dbf';

Database altered.

SQL> alter database recover managed standby database disconnect from session;

Database altered.

SQL>

The relocation of /u05/oradata/HRPRD/psindex04.dbf is the same as above.

3. Working on undo table space

Beside the steps for regular table space, we have to create a new undo table space undo02, then switch the current undo table space to undo02. After we finished the relocation, we drop undo02.
Primary side:

SQL> CREATE UNDO TABLESPACE undo02 DATAFILE '/u06/oradata/HRPRD/undo0201.dbf' SIZE 2048M AUTOEXTEND ON;


Tablespace created.

SQL> show parameter undo

NAME TYPE VALUE
------------------------------------ -------------------------------- ------------------------------
undo_management string AUTO
undo_retention integer 1800
undo_tablespace string psundo
SQL> alter system set undo_tablespace=undo02;

System altered.

SQL> alter tablespace psundo offline;

Tablespace altered.

SQL> !mv /u03/oradata/HRPRD/psundo03.dbf /u06/oradata/HRPRD/psundo03.dbf

SQL> alter tablespace psundo rename datafile '/u03/oradata/HRPRD/psundo03.dbf' to '/u06/oradata/HRPRD/psundo03.dbf';

Tablespace altered.

SQL> alter tablespace psundo online;

Tablespace altered.

SQL> alter system set undo_tablespace=psundo;

System altered.

SQL> drop tablespace undo02;

Tablespace dropped.

SQL>

Standby side:


SQL> alter database recover managed standby database cancel;

Database altered.

SQL> shutdown;
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.
SQL> !mv /u03/oradata/HRPRD/psundo03.dbf /u06/oradata/HRPRD/psundo03.dbf

SQL> startup mount;
ORACLE instance started.

Total System Global Area 570425344 bytes
Fixed Size 2072872 bytes
Variable Size 293605080 bytes
Database Buffers 268435456 bytes
Redo Buffers 6311936 bytes
Database mounted.
SQL> show parameter standby

NAME TYPE
------------------------------------ --------------------------------
VALUE
------------------------------
standby_archive_dest string
/ops_bkup/HRPRD/arch
standby_file_management string
AUTO
SQL> alter system set standby_file_management=MANUAL;

System altered.

SQL> alter database rename file '/u03/oradata/HRPRD/psundo03.dbf' to '/u06/oradata/HRPRD/psundo03.dbf';

Database altered.

SQL> alter system set standby_file_management=AUTO;

System altered.

SQL> alter database recover managed standby database disconnect from session;

Database altered.

SQL>

ORA-27300: OS system dependent operation:fork failed with status: 11

Got the following error in the alert log:


ORA-27301: OS failure message: Resource temporarily unavailable ORA-27302: failure occurred at: skgpspawn5 ORA-27300: OS system dependent operation:fork failed with status: 11 ORA-27301: OS failure message: Resource temporarily unavailable ORA-27302: failure occurred at: skgpspawn5 ORA-19583: conversation terminated due to error ORA-04030: out of process memory when trying to allocate 1052696 bytes (KSFQ heap,KSFQ Buffers) ORA-27300: OS system dependent operation:fork failed with status: 12 ORA-27301: OS failure message: Not enough space ORA-27302: failure occurred at: skgpspawn3

Solution: The problem was fixed by increasing the PGA from 399M to 500M.

Block change tracking on standby doesn't work

Today I asked how to turn on block tracking changing on physical standby side for Oracle 10g release 2. The Oracle support said it doesn't work even you turn it on.

Here is what they said:"
Block Change Tracking can be enabled at a physical standby database. However, you should note that changed blocks are not recorded, and incremental backups will not be faster during the physical standby as they are receiving and applying redo transactions from the primary database.

When the physical standby becomes a primary database, changes are once again recorded. Following the subsequent Level 0 backup, incremental backups take advantage of change tracking.

Your primary database block change tracking file would not get updated when you perform backup from standby. In 10.2, the CTWR process will only appear when the database is open. So even though you can enable block change tracking at a standby database, which will create the change tracking file, the CTWR process which is responsible for writing to the BCT filewill not start and the standby database will not record changes while the database is in recovery mode. It will start recording changes after the database is opened after a switchover or failover.

Refer Note.262853.1 Ext/Pub 10G RMAN Fast Incremental Backups."

I guess we still have one choice. It is to do the incremental backup at primary side. Since the block tracking changing on primary side will work, incremental backups at primary side may take much less time than the standby side. We can still perform the full backup at standby side as it takes the same amount of time as at primary side.

Temporary file problem for RMAN refresh (clone)

After using RMAN backup clone(refresh) a database, the temporary files don't work appropriatedly.

SQL> select file_name, tablespace_name from dba_temp_files;select file_name, tablespace_name from dba_temp_files *ERROR at line 1:ORA-01187: cannot read from file 1025 because it failed verification testsORA-01110: data file 1025: '/dcps01/oradata/fake/temp01.dbf'

Cause: This is because the previous temparary datafiles are there when refreshing. Note it's not a problem if the regular datafiles are there. RMAN will just overwrite existing datafiles. But for the temporay files, RMAN will skip it and give the above error.

Solution: Drop the temporary file and recreate them.

SQL> select name from v$tempfile;
NAME--------------------------------------------------------------------------------/dcps01/oradata/fake/temp01.dbf/dcps01/oradata/fake/pstemp01.dbf
SQL> alter database tempfile '/dcps01/oradata/fake/temp01.dbf' drop including datafiles;
Database altered.
SQL> alter database tempfile '/dcps01/oradata/fake/pstemp01.dbf' drop including datafiles;
Database altered.
SQL> alter tablespace temp add tempfile '/dcps01/oradata/fake/temp01.dbf' size 500M autoextend on next 100M maxsize 2048M;alter tablespace temp add tempfile '/dcps01/oradata/fake/temp01.dbf' size 500M autoextend on next 100M maxsize 2048M*ERROR at line 1:ORA-01119: error in creating database file '/dcps01/oradata/fake/temp01.dbf'ORA-27038: created file already existsAdditional information: 1
SQL> !rm /dcps01/oradata/fake/temp01.dbf
SQL> !rm /dcps01/oradata/fake/pstemp01.dbf
SQL> /
Tablespace altered.
SQL> alter tablespace pstemp add tempfile '/dcps01/oradata/fake/pstemp01.dbf' size 2048M;
Tablespace altered.
SQL> select file_name, bytes/1024/1024, tablespace_name from dba_temp_files;
FILE_NAME BYTES/1024/1024---------------------------------------- ---------------TABLESPACE_NAME------------------------------/dcps01/oradata/fake/temp01.dbf 500TEMP
/dcps01/oradata/fake/pstemp01.dbf 2048PSTEMP
SQL>

Install COBOL (Micro Focus Server Express 5.0) to Linux 5 (centos)

I found the installation is different from the instructions given in the People Tool installation guide. So I put the screens here.

[root@apps cobol]# sh install

This script will install Micro Focus Server Express 5.0 on this computer.

The readme.txt file included in this delivery contains details of
new features, enhancements and any restrictions of which you should
be aware. This file is located in :

/opt/lib/cobol/docs

We strongly recommend you read this file once the installation
is complete.

Do you want to continue (y/n): y

--------------------------------------------------------------------------------
Before installing and using this software product you must
agree to be bound by the terms and conditions of the end user
license agreement ("License Agreement") which accompanies this product.
Please take this time to read the License Agreement. If you are not in
agreement with the terms and conditions of the License Agreement, please
return the product to your Account Representative and your money will
be refunded. If you require a replacement copy of the License
Agreement, please contact your Account Representative before proceeding
with the install process.

Do you agree to the terms of the License Agreement? (y/n): y

--------------------------------------------------------------------------------
When you press return you will be shown details of the reference
environment (and any compatibility environments).

Please press return when you are ready:

This product is certified on the following reference environment:
The command(s) used to gather the information is given following each entry.

Operating System
----------------
Linux 2.6.9-11.ELsmp x86_64
Red Hat Enterprise Linux AS release 4 (Nahant Update 1)

uname -s
uname -r
uname -m
cat /etc/redhat-release

C Compiler
----------
cc gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)

gcc -v 2>&1 | tail -1

C++ Compiler
------------
/usr/bin/g++ gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)

g++ -v 2>&1 | tail -1

Assembler
---------
as GNU assembler version 2.15.92.0.2 (x86_64-redhat-linux) using BFD version 2.1
5.92.0.2 20040927

as -v 2>&1 < /dev/null

Linker
------
ld GNU ld version 2.15.92.0.2 20040927

ld -V 2>&1 | head -1

Supported versions of Java
--------------------------
Java version = 1.4.2_03
Java vendor = Sun Microsystems Inc.
Java OS name = Linux
Java OS arch = i386
Java OS version = 2.6.9-11.ELsmp

Java version = 1.5.0_06
Java vendor = Sun Microsystems Inc.
Java OS name = Linux
Java OS arch = i386
Java OS version = 2.6.9-11.ELsmp

Java version = 1.5.0_06
Java vendor = Sun Microsystems Inc.
Java OS name = Linux
Java OS arch = amd64
Java OS version = 2.6.9-11.ELsmp

$JAVA_HOME/bin/java -classpath $COBDIR/lib WhatJava

Unicode
-------
Unicode mapping tables must be installed for J2EE and Web Services to
function correctly. These tables are required for converting between
any combination of UTF-16/UCS-2, UTF-8 and other installed locales.

COBOL/J2EE Connectivity
-----------------------
COBOL/J2EE connectivity is supported on this Reference Environment with the
following Application Server products. :-

Jboss 3.2.8
Jboss 4.0.2
Oracle 10.1.2
Oracle 10.1.3
BEA WebLogic 9.0
IBM WebSphere 6.0

See the on-disk readme, $COBDIR/docs/readme.txt, for further information.

--------------------------------------------------------------------------------


This product is also certified on the following environment:


Operating System
----------------
Linux 2.6.9-11.ELsmp i686
Red Hat Enterprise Linux ES release 4 (Nahant Update 1)

uname -s
uname -r
uname -m
cat /etc/redhat-release

C Compiler
----------
cc gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)

gcc -v 2>&1 | tail -1


C++ Compiler
------------
/usr/bin/g++ gcc version 3.4.3 20050227 (Red Hat 3.4.3-22.1)

g++ -v 2>&1 | tail -1


Assembler
---------
as GNU assembler version 2.15.92.0.2 (i386-redhat-linux) using BFD version 2.15.
92.0.2 20040927

as -v 2>&1 < /dev/null


Linker
------
ld GNU ld version 2.15.92.0.2 20040927

ld -V 2>&1 | head -1


This product is also certified on the following environment:


Operating System
----------------
Linux 2.6.18-8.el5xen x86_64
Red Hat Enterprise Linux Server release 5 (Tikanga)

uname -s
uname -r
uname -m
cat /etc/redhat-release

C Compiler
----------
cc gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)

gcc -v 2>&1 | tail -1


C++ Compiler
------------
/usr/bin/g++ gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)

g++ -v 2>&1 | tail -1


Assembler
---------
as GNU assembler version 2.17.50.0.6-2.el5 (x86_64-redhat-linux) using BFD versi
on 2.17.50.0.6-2.el5 20061020

as -v 2>&1 < /dev/null


Linker
------
ld GNU ld version 2.17.50.0.6-2.el5 20061020

ld -V 2>&1 | head -1

Please confirm your understanding of the above reference environment
details (y/n): y

--------------------------------------------------------------------------------
Do you want to make use of COBOL and Java working together? (y/n): n
Skipping Java setup
Should you want to use Java with COBOL later on
as super user run the command /opt/lib/cobol/bin/java_setup
to select the version of Java you want to use.

--------------------------------------------------------------------------------
This product is protected using the Micro Focus License Management
Facility (LMF). Please refer to the Development System Licensing Guide
for information relating to the installation of the licensing system
and licenses.


If you do not have LMF installed or want to upgrade to the latest version,
we recommend you install it now.

Would you like to install LMF now? (y/n): y

Enter the directory name where you wish to install License Manager
(Press Enter for default directory /opt/microfocus/mflmf)

Do you want only superuser to be able to access the License Admin System? (y/n)
y
It is recommended that you let license manager autostart at boot time
Do you want license manager to be automatically started at boot time? (y/n)
y
LMF installation complete


Please consult the Development Licensing Guide for detailed information
on how to install licenses.

This may be done by changing directory to where the LMF was installed,
and typing
./mflicense


--------------------------------------------------------------------------------
To run your applications you need a deployment license installed using Apptrack.
See your Deployment Licensing Guide for details.
Installing Apptrack...

Access permissions on directory /var/mfaslmf have changed on this release
Write access permission has been removed except for superuser use
Apptrack installation complete


--------------------------------------------------------------------------------
This product can be used in either 32-bit or 64-bit modes.
Please enter either 32 or 64 to set the system default mode: 32
System default COBMODE has been set to 32.

--------------------------------------------------------------------------------
Installing documentation. Please wait...

--------------------------------------------------------------------------------
Enterprise Server provides a scalable, managed and high-performance
transactional environment for the deployment of COBOL applications
and services, COBOL/J2EE applications and direct COBOL Web Services.

Your Enterprise Server requires configuration. You can either do it now
or later. To do it now you need to know the alphanumeric user ID of the
Enterprise Server System Administrator.
To do it later, enter the following commands whilst logged in as root :
/opt/lib/cobol/bin/casperm
/opt/lib/cobol/bin/eslminstall

Do you wish to configure Enterprise Server now? (y/n): y

The use of Enterprise Server requires the Enterprise Server License Manager
to be running.

Do you want the Enterprise Server License Manager to be automatically
started at boot time? (y/n): y
Before continuing this installation, please ensure that you have the
alphanumeric user ID of the Enterprise Server System Administrator to hand.
You can find more information in the Configuration and Administration Guide.

Press 'q' to quit or return to continue:


The responses to the following questions will be used to help construct your
global transaction system configuration file (cas.cfg) - see your Configuration
and Administration Guide for more information.

Do you want error/warning messages to be displayed via the
syslog daemon? (y/n): y

Enter the alphanumeric user ID of the Enterprise Server System
Administrator.: root

Enter the directory where you want the Enterprise Server run-time system files
to reside. Please enter the absolute path. Do not use
environment variables. Press return to use /var/mfcobol/es


Setting file permissions. Please wait...
Processing -f option...

Enterprise Server configuration complete


--------------------------------------------------------------------------------
XDB is a fully-functional ANSI-compliant relational database
management system, providing support for SQL data access for
development purposes.

Do you want to install XDB? (y/n): y

Enter the directory where you want to install XDB.
Please enter the absolute path. Press return to use
/opt/microfocus/xdb

Installing XDB in directory /opt/microfocus/xdb...



Do you want to only install XDB client-side software (i.e. to work with an
existing XDB server installation)?n



Please enter the configuration directory (this should either not exist,
or be empty).
Press return for the default (/opt/microfocus/xdb/cfg) :
Please enter the configuration directory (this should either not exist,
or be empty).
Press return for the default (/opt/microfocus/xdb/cfg) :
Please enter the configuration directory (this should either not exist,
or be empty).
Press return for the default (/opt/microfocus/xdb/cfg) :
Please enter the configuration directory (this should either not exist,
or be empty).
Press return for the default (/opt/microfocus/xdb/cfg) :



Please enter the directory to store the XDB locations (this should either not
exist, or be empty).
Press return for the default (/opt/microfocus/xdb/locations) :



Please enter a unique name for the server.
Press return for the default of XDBSERVE:



Please enter the port number that the server should listen on.
Press return for the default of 8898:
Please enter the alphanumeric user ID under which all XDB processes
are to be executed: psoft

Your xdb server has been successfully configured. Please run either the
.xdbshrc or .xdbcshrc files created in directory:
/opt/microfocus/xdb/cfg
to set up the xdb environment. These scripts set up environment variables
and your path to enable you to use this server.

.xdbshrc is for Bourne type shell users (sh, bash, ksh, etc.)
use ". /opt/microfocus/xdb/cfg/.xdbshrc"

.xdbcshrc is for C type shell users (csh, tcsh, etc.)
use "source /opt/microfocus/xdb/cfg/.xdbcshrc"

The first time you start your server with the "xdbserve &" command, an
xdb system location will be created. The ampersand at the end of the
command is used to start the server as a background process. The
following messages will appear after the server is started:

Listening on port 8898.
Creating SYSTEM location, please wait...
SYSTEM location created.

Once the system location has been created, you will be able to use the
"xdbsql" command to log into the xdb server. Please create a new
location to store your tables in; the system location is used for
tracking the other locations the server manages. Please review the
README.locations file for more information.

To shut down the server, use the "xdbmon" command. The F10 key will
shut down the server from the "xdbmon" main menu. The zero key will
also function as the F10 key if you do not have your function keys
properly configured.

A batch script has been provided to create a tutorial location. It can
be invoked with the xdbsql command as follows:

xdbsql --batch /opt/microfocus/xdb/share/mktutorial.sql

You will be prompted to enter a directory create the tutorial location in.
The subdirectory "tutorial" will be appended to the path that you enter.


XDB installation complete.

--------------------------------------------------------------------------------
(remember to set COBDIR to /opt/lib/cobol,
include /opt/lib/cobol/lib in LD_LIBRARY_PATH
and include /opt/lib/cobol/bin on your PATH)


WARNING: Any executables (whether a Run-Time System or an application)
must be relinked using this new release. Otherwise, the results of
running the older executables with this new release are undefined.

Installation completed successfully.

The COBOL system is ready to use.
[root@apps cobol]#

ORA-01801: date format is too long for internal buffer while resync catalog

While doing resync catalog in RMAN, getting the following error:
RMAN> list incarnation;
starting full resync of recovery catalogRMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of list command at 04/29/2008 15:41:19RMAN-03014: implicit resync of recovery catalog failedRMAN-03009: failure of full resync command on default channel at 04/29/2008 15:41:19ORA-01801: date format is too long for internal buffer

Note the resync catalog can be implicly called by other command like reset database, list incarnation, list backup, etc.

Solution:
Change the date format at the recovery catalog and restart.
SQL> alter system set nls_date_format='YYYY-MM-DD:HH24:MI:SS' scope=spfile;
System altered.
SQL> shutdown immediate;Database closed.Database dismounted.ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []SQL> startupORACLE instance started.
Total System Global Area 784334848 bytesFixed Size 2074504 bytesVariable Size 423626872 bytesDatabase Buffers 352321536 bytesRedo Buffers 6311936 bytesDatabase mounted.Database opened.
SQL>

Reconnect to rman and then the problem is fixed.
RMAN> exit
Recovery Manager complete.$ rman target sys/password@anly3trn catalog rman/rman@catdev
Recovery Manager: Release 10.2.0.2.0 - Production on Tue Apr 29 15:48:11 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ANLY3TRN (DBID=25363641)connected to recovery catalog database
RMAN> resync catalog;
starting full resync of recovery catalogfull resync complete
RMAN>

PeopleSoft HCM9.0 Installation troubleshooting

Peoplesoft installation notes
Order of Installation
1．Oracle Database Software
2．Tuxedo
3．PeopleTools on Linux
4．PeopleTools on Windows
5．Create Oracle Database then PeopleSoft Database
6．Web Server
7．PIA
8．People Books
Database installation
1. Error message when run installer:　
Exception java.lang.UnsatisfiedLinkError: /tmp/OraInstall2007-08-19_03-55-00PM/jre/1.4.2/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory occurred..
java.lang.UnsatisfiedLinkError: /tmp/OraInstall2007-08-19_03-55-00PM/jre/1.4.2/lib/i386/libawt.so: libXp.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.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at sun.security.action.LoadLibraryAction.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(Unknown Source)
at sun.awt.DebugHelper.(Unknown Source)
at java.awt.Component.(Unknown Source)

Fix:
Download from http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/Fedora/RPMS/
Apply the patch.
[root@apps paches]# rpm -Uvh libXp-1.0.0-8.i386.rpm

Tuxedo installation
Error:
Installing...

awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/tmp/install.dir.3940/Linux/resource/jre/bin/java: error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or directory
Tuxedo 9.1 base installation complete

Fix:
-bash-3.1$ cd linux/sles9/base
-bash-3.1$ cp tuxedo91_32_SLES_9_x86.bin tuxedo91_32_SLES_9_x86.bin.bak
-bash-3.1$ cat tuxedo91_32_SLES_9_x86.bin.bak sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/" >tuxedo91_32_SLES_9_x86.bin
-bash: tuxedo91_32_SLES_9_x86.bin: Permission denied
-bash-3.1$ cat tuxedo91_32_SLES_9_x86.bin.bak sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/" >tuxedo91_32_SLES_9_x86.bin

Linux patches: http://rpmfind.net/linux/rpm2html/search.php?query=unixODBC-devel&submit=Search+...&system=&arch=

-bash-3.1$ sh install.sh

01) ibm/aix53 02) linux/sles9 03) setup/5045158435a38b48dea252fdca98f9b3
04) setup/9f00655a86fb2b6696a2082837e1820805) sun/sol9

Please select a platform? [1-5, q to quit, l for list]: 2

Installing for linux/sles9

Is this correct? [y,n,q]: y
cp: cannot create regular file `/tmp/lic.txt': Permission denied

If you wish to quit the installation at any point
press the interrupt key or .
BEA Home being defaulted to /bea (y/n)
n
Please supply alternative BEA Home:
/psft/bea
Tuxedo 9.1 will be installed to /psft/bea/tuxedo91 (y/n):
y
Accept default TListen password 'password' (y/n):
y
Continue with installation of Tuxedo 9.1 (y/n):
y
Installing...

awk: cmd. line:6: warning: escape sequence `\.' treated as plain `.'
Tuxedo 9.1 base installation complete
Installing patch at /psft/bea/tuxedo91
using /bin/gunzip to uncompress archive
Installing server and client files...
Enter owner for patch files:
psofthr
Enter group for patch files:
psoft

The patch installation finished successfully.
-bash-3.1$

People tools installation
Error:
Fix: use command unzip –t zipfilename to check which file is broken during download. Download the broken files and reinstall.
Web Logic installation.

Stuck on
Installing PeopleSoft license for WebLogic Server 9.2 (Step 1 of 2)
Please wait and do not interrupt ....

Done!

Updating license registry. (Step 2 of 2)

Fix: haven’t found out the fix yet. But instead, use Oracle Application Server.
HRMS installation

When launching the installation, get the following error:
Running InstallShield Wizard...
The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag.

Fix: Just run it in nongraph mode.

Installing Peopletools on Windows

Errors occurred during the installation.

One or more errors occurred during the copying of files (eel_complat_comp_files) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (bean459) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (complat_emf_files) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (nt_emf_files) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (bean260) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (langpack_appbatch_files) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (langpack_batchfile_files) . Please refer to the install log for additional information.
One or more errors occurred during the copying of files (bean542) . Please refer to the install log for additional information.

Fix: Check downloaded files and redownload corrupted files.

Install HRMS
Errors occurred during the installation.

One or more errors occurred during the copying of files
(bean_hcsys_ComPlat_DBFile_bse) . Please refer to the install log
for additional information.
One or more errors occurred during the copying of files
(bean_hcdmo_ComPlat_DBFile_bse) . Please refer to the install log
for additional information.

Fix: Check the downloaded file and the extracted file. Some file are broken.

Creating the database:

Hanging

Fix:

1. Kill the process.
2. Delete all tables of SYSADM.
3. Delete the record of ps.psdbowner
4. Start over again.

Upgrading PeopleSoft Database
While connect to the database using data mover and user PS/PS,
Fix:
grant connect to ps;
revoke connect from ps;

Starting Application Server
While starting app server, get
9 processes started.
Checking process startup status. Please wait.

Some processes failed to complete initialization. tmshutdown -qy



==============ERROR!================
Boot attempt encountered errors!. Check the TUXEDO log for details.
==============ERROR!================

Do you wish to see the error messages in the APPSRV.LOG file? (y/n) [n] :

Fix:
Check app server log and it says
PSADMIN.20354 (0) [10/25/07 09:06:44](0) Begin boot attempt on domain psdmo
PSWATCHSRV.20364 (0) [10/25/07 09:06:53] Checking process status every 120 seconds
PSWATCHSRV.20364 (0) [10/25/07 09:06:53] Server started
PSSAMSRV.20368 (0) [10/25/07 09:06:59](0) PeopleTools Release 8.49 (Linux) starting
PSSAMSRV.20368 (0) [10/25/07 09:06:59](0) Cache Directory being used: /psft/PT8.49/appserv/psdmo/CACHE/PSSAMSRV_100/
PSSAMSRV.20368 (0) [10/25/07 09:06:59](1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
PSSAMSRV.20368 (0) [10/25/07 09:06:59](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PSDMO with user PS.
PSSAMSRV.20368 (0) [10/25/07 09:06:59](0) Server failed to start
PSAPPSRV.20366 (0) [10/25/07 09:07:01](0) PeopleTools Release 8.49 (Linux) starting
PSAPPSRV.20366 (0) [10/25/07 09:07:01](0) Cache Directory being used: /psft/PT8.49/appserv/psdmo/CACHE/PSAPPSRV_2/
PSAPPSRV.20366 (0) [10/25/07 09:07:01](1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
PSAPPSRV.20366 (0) [10/25/07 09:07:01](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PSDMO with user PS.
PSAPPSRV.20366 (0) [10/25/07 09:07:01](0) Server failed to start
PSAPPSRV.20365 (0) [10/25/07 09:07:01](0) PeopleTools Release 8.49 (Linux) starting
PSAPPSRV.20367 (0) [10/25/07 09:07:01](0) PeopleTools Release 8.49 (Linux) starting
PSAPPSRV.20367 (0) [10/25/07 09:07:01](0) Cache Directory being used: /psft/PT8.49/appserv/psdmo/CACHE/PSAPPSRV_3/
PSAPPSRV.20367 (0) [10/25/07 09:07:01](1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
PSAPPSRV.20367 (0) [10/25/07 09:07:01](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PSDMO with user PS.
PSAPPSRV.20367 (0) [10/25/07 09:07:01](0) Server failed to start
PSAPPSRV.20365 (0) [10/25/07 09:07:01](0) Cache Directory being used: /psft/PT8.49/appserv/psdmo/CACHE/PSAPPSRV_1/
PSAPPSRV.20365 (0) [10/25/07 09:07:01](1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora (200,0)
PSAPPSRV.20365 (0) [10/25/07 09:07:01](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PSDMO with user PS.
PSAPPSRV.20365 (0) [10/25/07 09:07:01](0) Server failed to start
PSWATCHSRV.20364 (0) [10/25/07 09:07:02] Shutting down
PSADMIN.20354 (0) [10/25/07 09:07:08](0) End boot attempt on domain psdmo

Check stderr under /psft/PT8.49/appserv/psdmo and it shows
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora.so': libclntsh.so.9.0: cannot open shared object file: No such file or directory

Login as user oracle and go to $PS_HOME/bin. Make a soft link as
-bash-3.1$ ln -s /u01/app/oracle/product/10.2.0/db/lib/libclntsh.so.10.1 libclntsh.so.9.0

Another issue:

Tuxedo log says:
013438.lserv!PSANALYTICSRV.26625.3086825152.0: LIBTUX_CAT:681: ERROR: Failure to create message queue
013438.lserv!PSANALYTICSRV.26625.3086825152.0: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = : msgget: No space left on device
013535.lserv!tmboot.26647.3086337728.-2: 10-28-2007: Tuxedo Version 9.1, 32-bit
013535.lserv!tmboot.26647.3086337728.-2: CMDTUX_CAT:1851: INFO: TM_BOOTTIMEOUT is set to 60 seconds
013535.lserv!tmboot.26647.3086337728.-2: CMDTUX_CAT:1855: INFO: TM_BOOTPRESUMEDFAIL option is selected
013536.lserv!PSRENSRV.26648.3086419648.-2: 10-28-2007: Tuxedo Version 9.1, 32-bit
013536.lserv!PSRENSRV.26648.3086419648.-2: LIBTUX_CAT:681: ERROR: Failure to create message queue
013536.lserv!PSRENSRV.26648.3086419648.-2: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = : msgget: No space left on device
013536.lserv!tmboot.26647.3086337728.-2: CMDTUX_CAT:825: ERROR: Process PSRENSRV at lserv failed with /T tperrno (TPEOS - operating system error)
013536.lserv!tmboot.26647.3086337728.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
013536.lserv!tmshutdown.26649.3086218944.-2: 10-28-2007: Tuxedo Version 9.1, 32-bit
013536.lserv!tmshutdown.26649.3086218944.-2: LIBTUX_CAT:681: ERROR: Failure to create message queue
013536.lserv!tmshutdown.26649.3086218944.-2: FATAL: internal error: CMDTUX_CAT:764: ERROR: can't attach to BB
013536.lserv!tmboot.26647.3086337728.-2: FATAL: CMDTUX_CAT:828: ERROR: Cannot create error process - fork() failed

Fix:

Edit /etc/sysctl.conf and add the parameter
kernel.msgmin = 50
run command sysctl –p .

Installing Oracle Application Server
07/10/28 11:51:12 Start process
--------
/psft/product/10.1.3.1/OracleAS_1/Apache/Apache/bin/apachectl startssl: execing httpd
/psft/product/10.1.3.1/OracleAS_1/Apache/Apache/bin/httpd: error while loading shared libraries: libdb.so.2: cannot open shared object file: No such file or directory

Fix: Download and apply the patch db1-1.85-0.3.i386.rpm
http://www.megaloman.com/~hany/RPM/doors2.4/jr/db1-1.85-0.3.i386.html

RMAN incremental backup is stupid

I set up RMAN full backup on Sunday and incremental accumulative backup on the rest of the week. It works perfect but after the full backups failed one day, I got problems. The problem is the incremental backups takes more space than the level 0 full backups everyday. So soon I ran out of disk space.

I missed the level 0 backup on Sunday and when the RMAN do incremental level 1 backup on Monday, it actually do a full backup. It's fine since it can not find a full backup. But on Tuesday, it do a full backup again even I already have a full backup, which is Monday's level 1 backup. On Wednsday, it do a full backup again.

I know it will not happen if we do incremental differential backup. But hell! Why RMAN can't be design smart enough to recognize the Monday's level 1 backup is actually a full backup!

How to improve incremental backups

I set up the RMAN backup for the company I am working. One thing I always try to figure out is why the incremental backups takes more time than the full backup. I do a full backup on Sunday and do an incremental level 1 backup everyday. But the incremental backup takes 2 hours while the full backup only takes about 1 hour. Today I figured out a way.

Login with sqlplus as sysadba,

alter database enable block change tracking using file '$ORACLE_BASE/admin/bct/bct.dbf';

Then guess what, the incremental backups starts takeing 8 minutes!

Check the status:

select * from v$block_change_tracking;

You can disable it by

alter database disable block change tracking.