Title: |
| |
Description: |
| |
Query: |
|
Sunday, December 30, 2012
Query to find the Activity Status of the workflow
What is wdbsvr.app file used for? What's full path of this file? What's significance of this file ?
Q. What is wdbsvr.app file used for? What's full path of this file? What's significance of this file ?
I'll again suggest you don't just remember answer & try to solve mystery behind this file. First where this file exists ? You can find this file under $IAS_ORACLE_HOME/Apache/modplsql/cfg
Based on file location I am sure you can say this is related to Apache, & looking into modplsql/cfg , I am sure you will say its related to mod_pls (mod plsql component of Apache/Oracle 11i WebServer) configuration file. This file is used by mod_plsql component of Apache to connect to database. So when you type url http://hostname:port/pls/SID , whenever Apache(11i Web Server) finds that request is for /pls/ then Apache delegates this request to mod_pls component which in turn pick this file & check if there is any DAD with name SID (in our example its VISION11I) &
Sample entry in wdbsvr.app
[DAD_VISION11I]
connect_string = VISION11I
password = apps
username = APPS
default_page = fnd_web.ping
On typing http://hostname:port/pls/VISION11I , it will connect to database using apps schema & will return you page fnd_web.ping ( where fnd_web is package & ping is procedure or vise versa).
So story about this file doesn't stop here , this url which I mentioned about is quite useful in troubleshooting so you can check if database connection is working fine or not. Another thing you want to check about this file is since it stores APPS password you need to change here whenever you change apps password.
Oracle iSetup - Frequently Asked Questions
Oracle iSetup - Frequently Asked Questions
1. Do you have to buy iSetup, is it licensed separately?
A. iSetup is free and comes embedded with the base EBS R12 image.
B. For 11.5.10 and later you have to apply a patch AZ.H to enable iSetup
C. iSetup exists in 11.5.9 versions also. But in 11.5.10, iSetup got a totally new makeover with two main components, namely iSetup Migrator and iSetup Reporter. iSetup version AZ.H is what we recommend our customers to uptake
2. What is the difference between iSetup and FNDLOAD
A. iSetup is used to migrate functional configuration data, whereas FNDLOAD is an utility for packaging seed data. iSetup supports multiple types of interfaces like BC4J, Business Service Objects and FNDLOAD. iSetup offers additional benefits such as load sequencing and reporting capabilities on top of FNDLOAD APIs.
3. Can iSetup be used to upgrade from 11i to R12
A. iSetup cannot be used to migrate data from 11i to R12 instance directly. Instead, you can upgrade source instance from 11i to R12 and then use iSetup to migrate data to R12 target instance.
4. What are the pre-requisites for iSetup
A. Patch set level - For iSetup, it is recommended that all the instances should be on the same patch level. At a minimum, ATG PF RUP should be at the same level.
B. User - Source and target instance should have the same 'User' with iSetup responsibility.
C. Source and target instances should have each other's latest 'dbc files' under $FND_SECURE directory.
5. Can iSetup migrate objects other than those provided out of the box
A. iSetup allows users to define Custom selection sets, where interfaces of type Business Service Objects, Generic Loader, BC4J and custom java classes can be added to create migration templates in addition to the seeded templates.
6. I have Logical Apps, what should I use for my EBS setup migrations now: iSetup or Logical Apps?
A. Oracle supports both iSetup and LogicalApps for migration of 11i EBS setups. To migrate R12 setups, the recommendation is to use iSetup. Strategic focus of iSetup will be to accelerate EBS rollouts using the setup migration and reporting features. Primary focus of Logical Apps Configuration Controls Governor (CCG) will be to detect, control and remediate application configuration change, enterprise-wide.
7. What is the difference between iSetup and Oracle Business Accelerator?
A. Oracle Business Accelerators are powerful, easy-to-use rapid implementation solutions for Oracle E-Business Suite and JD Edwards EnterpriseOne customers through Oracle's approved partner channel or Oracle Consulting. Available in industry-specific versions for more than 20 industries, they make initial configuration of Oracle E-Business Suite simple, fast, and predictable.
B. iSetup on the other hand is a tool that helps migrate functional configurations, it does not perform configuration activities
C. Both these tools are complementary in nature
8. Is iSetup like any other ETL tool
A. The USP of iSetup is that it performs key business validations while extracting and loading setup data. iSetup also enforces the sequence in which the setup objects need to loaded, out of the box.
9. Does iSetup help in configuring new EBS instance?
A. No. iSetup does not help in configuring new EBS instances from scratch. However, iSetup can be used to configure new EBS instance using the setup data from an existing EBS instance or an iSetup Extract.
10. Are there any plans to extend the coverage to other product families? If yes, what are the timelines that we are talking about?
A. iSetup currently offers selection sets covering the APIs listed for:
i) Foundation Suite
ii) Financial Suite
iii) Discrete manufacturing and Distribution suite
iv) HRMS suite
Product coverage is enhanced in every release, and is prioritized on a customer requirement basis.
11. Are there any plans for the migration of the configuration in languages other than English?
A. Not all interfaces support migration of MLS data. There are plans to enhance this coverage, and is prioritized on a customer requirement basis.
12. Are there any plans to open iSetup more as a framework to handle customized setups in implementation projects?
A. Yes we can support custom interfaces written as per iSetup Framework, if interested, please get in touch with us.
13. Filter & transformation are not supported for most of the selection sets? Are there any plans to open-up the same for super user responsibility?
A. Yes
14. Can I transform setups offline using Excel?
A. This is being planned as an enhancement for future releases
Oracle iRecruitment (iRec) External Candidate (Site Visitor) Configuration & Login Steps
Oracle iRecruitment (iRec) External Candidate (Site Visitor) Configuration & Login Steps
1. Make sure that you are using seeded iRecruitment External candidate responsibilities.
2. Set the SSO Profile settings with the values.
Applications SSO Login Types - Both
Applications SSO Type - SSWA
Applications SSO User Creation and Updation Allowed - Enabled
Application SSO LDAP Synchronization - Enabled
3. Schedule the following concurrent processes:
• iRecruitment Index Synchronization
This ensures the job posting and document indexes are kept up to date and should be scheduled to run as follows:
- Online index rebuild - to run every 5 minutes
- Full index rebuild - to run each night
• Synchronize WF Roles
4. Check the IRC: Registration Business Group profile pointing to a correct business group for the iRecruitment External candidate Responsibility.
5. Add site visitor responsibilities to your Guest user Assign the iRecruitment Employee Site Visitor and iRecruitment External Site Visitor responsibilities
to your guest user (identified by the Guest User Password profile option). This step is required to allow access to the site visitor screens without logging in to the application.
6. Also, download IrcVisitor.jsp page from the server and open the page in text editor and check if the Responsibility ID of 'iRecruitment Site Visitor' login page pointing to upon login. Pointing to a correct responsibility and this responsibility should be pointing in the login jsp page.
7. Set up proxy server
Use the following profiles to set up your proxy server:
• Applications Server Side Proxy Host and Domain
• Applications Proxy Bypass Domain
• IRC: Proxy Authorization Password
• IRC: Proxy Authorization User Name
8. Configure and Freeze your flexfields Configure and Freeze all flexfields used in iRecruitment. This stops error messages appearing on the screen telling you that your flexfields have not been frozen.
9. Check the log-in URL for iRecruitment users The URL for connecting to the iRecruitment system varies according to the user group. For example, the internal site visitor URL is different from the external site visitor URL. For external site visitors, you access the IrcVisitor.jsp. The location of this jsp will depend on your applications server, however, it is of the form: http://hostname:port/OA_HTML/IrcVisitor.jsp For internal site visitors, you access the IrcEmpVisitor.jsp. The location of this jsp also depends on your applications server, however, it is of the form:
http://hostname:port/OA_HTML/IrcEmpVisitor.jsp
You should replace the http://hostname:port/OA_HTML part of the URL with the URL of the html directory on your applications server.
Note: If you have installed other languages, you activate iRecruitment in the required language by adding the following suffix to the log-in URLs: ?L=<language code>
For example, http://hostname:port/OA_HTML/IrcVisitor.jsp?L=F would activate the French language version. The language codes are available in the table FND_INSTALLED_LANGUAGES. If you do not specify a language code, the default (US) is used
10. Configure the web pages for iRecruitment You configure the web page layout using the Personalization Framework. If applicable, configure flexfields, instructions and tips, and the delivered logos.
How SSL works with Middle Tier Oracle HTTP Server
How SSL works with Middle Tier Oracle HTTP Server:
1. The client sends a request to the server using HTTPS connection mode.
2. The server presents its certificate to the client. This certificate contains the server's identifying information.
3. The client checks its list of Trust points and compares the information in the certificate with the server's public key. If it matches, the server is authenticated as a trusted server.
4. The client sends the server a list of the encryption levels, or ciphers, that it can use.
5. The server receives the list and selects the strongest level of encryption that they have in common.
6. The client creates a session key which is used to encrypt the data and sends this session key to the server which can decrypt the data with its private key
Enabling SSL in Oracle E-Business Suite Release 12
The most significant change for Secure Sockets Layer (SSL) support in E-Business Suite Release 12 is the use of the mod_ossl module for the Oracle HTTP Server. Like mod_ssl, the mod_ossl plug-in enables strong cryptography for Oracle HTTP Server. In contrast to the OpenSSL module, mod_ossl is based on the Oracle implementation of SSL, which supports SSL 3, and is based on Certicom and RSA Security technology.
In Release 12 SSL certificates will be managed by the Oracle Wallet Manager 10g, which will be accessible via the familiar OWM graphical user interface (GUI) or the new ORAPKI command line interface (CLI). Since Release 12 will be using the Forms Listener Servlet a separate certificate is no longer needed for Forms. Forms will share the same wallet as the Oracle HTTP Server.
BACKUP AND RECOVERY PLAN USING RMAN
Backup and Recovery Plan Using RMAN
Environment
Hostname: earth02
Unix Owner: oratst
RMAN environment: ${ORACLE_HOME}/RMAN_earth02.env
Scripts: /u12/maint_scripts/rman_scripts
Backup Directory: /u12/data/<SID>
target database Database you want to backup using RMAN
catalog Rman repository
Misc Recovery Details
v After recovering control file you must reset database to a new incarnation in RMAN catalog - Note:175768.1
v Consistent backup Database mounted but not open. Database was not shutdown with abort command or crashed.
v Inconsistent backup Requires media recover but is as valid as a consistent backup
v Verify NLS_DATE and NLS_LANG are the same in rman and target database
NLS_LANG="AMERICAN_AMERICA.WE8ISO8859P1"
export NLS_LANG
NLS_DATE_FORMAT="DD-MON-YYYY HH24:MI:SS"
export NLS_DATE_FORMAT
v Default Device Format for test
Configure channel device type disk format ='/u12/data/bkup_%U';
RMAN Requirements
RMAN with Legato
1. Install NMO on Client (Networker Module for Oracle)
a. Backup Command: (nsrnmo script to run RMAN from Legato):
script : /usr/sbin/nsrnmo9i
owner : root
2. Rman backup scripts
a. Saveset:
script location : /u12/maint_scripts/rman_scripts
owner : oraprd
Setup Target Database to use RMAN
1. Set target database to archivelog mode
Startup mount
alter database archivelog;
alter database noarchivelog;
alter database open
Alter system archive log start
2. Create a password file (for sysdba remote connection)
Orapwd file=orapwSID password=<password> entries=10
3. Add line to init.ora file:
Remote_login_passwordfile=exclusive
4. Create a sysdba user in Target for RMAN connection
Create user rman identified by rman
Default tablespace tools
Default temp tablespace temp;
Grant create session, sysdba to rman;
Setup RMAN instance to use Catalog
1. Create RMAN instance
Create tablespace for catalog
Update tnsnames.ora with databases that will use RMAN
2. Create RMAN user:
grant recovery_catalog_owner to rman;
grant connect,resource,sysdba to rman
3. Create rman catalog
rman catalog rman/rman@rman msglog = catalog.log
create catalog tablespace 'CATALOG';
exit;
4. Register database:
source SID.env OF database with Updated TNSNAMES.ora
>rman target rman/rman9@<ORACLE_SID>
>connect catalog rman/rman@rman
>register database;
Rman Commands
a. Connect to rman
rman catalog rman/rman9@rman target rman/rman9@target
b. Show default configuration
Connect to target and rman:
rman catalog rman/rman9@rman
RMAN> target rman/rman9@tcmdb
RMAN> SHOW ALL; (Default)
Automatic Configuration Environment:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 3;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(NSR_DATA_VOLUME_POOL=HADallasUnixTest)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u10/oracle/testdb/9.2.0/dbs/snapcf_TCMDB.f';
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u10/oracle/testdb/9.2.0/dbs/snapcf_TCMDB.f'; # default
Parameters in PROD_US
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 3;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(NSR_DATA_VOLUME_POOL=HADallasRmanUnix)';
CONFIGURE MAXSETSIZE TO 2097152 K;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/oracle/proddb/9.2.0/dbs/snapcf_PROD.f'; # default
b. Commands to find information required for Recovery
unregister database;
execute dbms_rcvcat.unregisterdatabase (db_key, db_id)
Find db_key db_id:
select * from rc_database;
Recreate snapshot controlfile destination from target as sys:
execute sys.dbms_backup_RESTORE.CFILESETSNAPSHOTNAME('/u10/oracle/prddb/9.2.0/dbs/snapcf_PBIR.f'); execute
1. Check Log #'s:
select max(next_change#) scn
from v$archived_log
group by thread#;
select max(next_change#)
from v$archived_log
where archived='YES'
group by thread#;
select max(next_change#) from v$log_history;
1145081 1145082 263561676 PBIR
2. select * from rc_database_incarnation;
dbkey=2832
a. select dbinc_key, dbid,resetlogs_change# from rc_database_incarnation 2;
Find the seq# of the CATALOGED archived log files
Query the RMAN catalog:
3. select i.DBID,a.DB_KEY,a.DBINC_KEY,a.DB_NAME,SEQUENCE#,a.FIRST_CHANGE#,a.NEXT_CHANGE#,a.COMPLETION_TIME,a.STATUS
from RC_ARCHIVED_LOG a, rc_database_incarnation i
where a.DBINC_KEY = i.DBINC_KEY and i.CURRENT_INCARNATION='YES'
and i.DBID=1519956463
order by SEQUENCE#;
c. Commands to maintain Recovery Catalog
allocate channel for maintenance device type disk;
allocate channel for maintenance device type sbt;
crosscheck backup;
crosscheck copy;
delete expired backup;
delete expired copy;
release channel;
allocate channel for maintenance device type sbt;
delete obsolete;
release channel;
d. Additional RMAN commands:
a. reset database (Used after recovering control file) Note:175768.1
b. List incarnation of database;
c. Reset database to incarnation inc_key:;
You can run a test RMAN backup that does not generate
any output. The test checks datafiles for physical and logical corruption and
that all database files exist and are in the correct locations
d. BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
.
e Create an image copy
COPY DATAFILE 1 TO '/tmp/df1.cpy', CURRENT CONTROLFILE TO '/tmp/cf.cpy';
Recovery Scenarios
1. Restore Control file
startup mount;
restore controlfile;
alter database mount;
# you must run the RECOVER command after restoring a control file even if no datafiles require recovery
recover database;
alter database open resetlogs;
# if the database uses locally -
Did not run until time:
restore with either until time or last backup:
run {
2> set until time '19-JUN-2003 15:39:56';
3> allocate channel t1 type 'SBT_TAPE';
4> restore controlfile;
Ran the following script to restore control file:
v Recover control file script: TCMDB_recover_ctrlfile.rcv
run {
allocate channel D1 type DISK;
restore controlfile;
alter database mount;
recover database;
}
JAMES' version
SCRIPT: BUTEST_recover_ctrlfile.rcv
connect rcvcat rman/rman9@rman
Connect target rman/rman9@butest
#
# Need to know the name of the backup you are pulling from
#
run {
allocate channel t1 type 'SBT_TAPE'
parms 'ENV=(NSR_DATE_VOLUME_POOL=HADallasUnixTest, NSR_DEBUG_FILE=/tmp/recover_BUTEST_ctrlfile.log)';
restore controlfile from 'bu_BUTEST_s3p1t564339234_03gq67hq'
}
Perform a normal database recovery at that point.
2. Recover dropped system datafile
Recover a dropped datafile
RUN
{
SQL 'ALTER DATABASE DATAFILE 7 OFFLINE';
# To restore to a different location, uncomment the following command.
# SET NEWNAME FOR DATAFILE 7 TO '/newdir/new_filename.f';
RESTORE DATAFILE 7;
# If you restored to different locations, uncomment the following line.
# SWITCH DATAFILE ALL;
RECOVER DATAFILE 7;
SQL 'ALTER DATABASE DATAFILE 7 ONLINE';
}
Clone Database:
The cloned database is referred to as the Auxillary database in Rman
Setup Auxillary database environment the same as environment as the Target Database.
Add these entries to the init.ora file of the cloned database.
Recover Scenario Output
Clone database:
Recovery Manager: Release 9.2.0.5.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect catalog rman/rman9@RMAN;
2> connect target rman/rman9@TCMDB;
3> connect auxiliary sys/m1rage@NEWDB;
4>
5> #
6> # Clone the TCMDB database to NEWDB on the same machine
7> #
8>
9> run {
10> allocate auxiliary channel t1 type DISK;
11> allocate channel d1 type DISK;
12> set until SCN 27819646;
13> duplicate target database to NEWDB;
14> }
15>
connected to recovery catalog database
connected to target database: TCMDB (DBID=2386221693)
connected to auxiliary database: NEWDB (not mounted)
allocated channel: t1
channel t1: sid=11 devtype=DISK
allocated channel: d1
channel d1: sid=15 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 15-NOV-05
printing stored script: Memory Script
{
set until scn 27819646;
set newname for datafile 1 to
"/u09/oracle/newdbdata/system01.dbf";
set newname for datafile 2 to
"/u11/oracle/newdbdata/undotbs01.dbf";
set newname for datafile 3 to
"/u11/oracle/newdbdata/writerd01.dbf";
set newname for datafile 4 to
"/u09/oracle/newdbdata/writerx01.dbf";
set newname for datafile 5 to
"/u11/oracle/newdbdata/writerrepod01.dbf";
set newname for datafile 6 to
"/u09/oracle/newdbdata/writerrepox01.dbf";
set newname for datafile 7 to
"/u11/oracle/newdbdata/ovdbd01.dbf";
set newname for datafile 8 to
"/u09/oracle/newdbdata/ovdbx01.dbf";
set newname for datafile 9 to
"/u11/oracle/newdbdata/tools01.dbf";
set newname for datafile 10 to
"/u11/oracle/newdbdata/sdd01.dbf";
set newname for datafile 11 to
"/u09/oracle/newdbdata/sdx01.dbf";
set newname for datafile 12 to
"/u11/oracle/newdbdata/rdd01.dbf";
set newname for datafile 13 to
"/u09/oracle/newdbdata/rdx01.dbf";
set newname for datafile 14 to
"/u11/oracle/newdbdata/cmgmtd01.dbf";
set newname for datafile 15 to
"/u11/oracle/newdbdata/sdeskd01.dbf";
set newname for datafile 16 to
"/u09/oracle/newdbdata/sdeskx01.dbf";
set newname for datafile 17 to
"/u09/oracle/newdbdata/cmgmtx01.dbf";
restore
check readonly
clone database
;
}
executing script: Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 15-NOV-05
channel t1: starting datafile backupset restore
channel t1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u09/oracle/newdbdata/system01.dbf
restoring datafile 00004 to /u09/oracle/newdbdata/writerx01.dbf
restoring datafile 00007 to /u11/oracle/newdbdata/ovdbd01.dbf
restoring datafile 00011 to /u09/oracle/newdbdata/sdx01.dbf
channel t1: restored backup piece 1
piece handle=/u12/data/TCMDB/bu_TCMDB_j3h3qftu tag=TAG20051115T142918 params=NULL
channel t1: restore complete
channel t1: starting datafile backupset restore
channel t1: specifying datafile(s) to restore from backup set
restoring datafile 00003 to /u11/oracle/newdbdata/writerd01.dbf
restoring datafile 00005 to /u11/oracle/newdbdata/writerrepod01.dbf
restoring datafile 00014 to /u11/oracle/newdbdata/cmgmtd01.dbf
restoring datafile 00015 to /u11/oracle/newdbdata/sdeskd01.dbf
channel t1: restored backup piece 1
piece handle=/u12/data/TCMDB/bu_TCMDB_j4h3qg0t tag=TAG20051115T142918 params=NULL
channel t1: restore complete
channel t1: starting datafile backupset restore
channel t1: specifying datafile(s) to restore from backup set
restoring datafile 00002 to /u11/oracle/newdbdata/undotbs01.dbf
restoring datafile 00009 to /u11/oracle/newdbdata/tools01.dbf
restoring datafile 00010 to /u11/oracle/newdbdata/sdd01.dbf
restoring datafile 00012 to /u11/oracle/newdbdata/rdd01.dbf
channel t1: restored backup piece 1
piece handle=/u12/data/TCMDB/bu_TCMDB_j5h3qg10 tag=TAG20051115T142918 params=NULL
channel t1: restore complete
channel t1: starting datafile backupset restore
channel t1: specifying datafile(s) to restore from backup set
restoring datafile 00006 to /u09/oracle/newdbdata/writerrepox01.dbf
restoring datafile 00008 to /u09/oracle/newdbdata/ovdbx01.dbf
restoring datafile 00013 to /u09/oracle/newdbdata/rdx01.dbf
restoring datafile 00017 to /u09/oracle/newdbdata/cmgmtx01.dbf
channel t1: restored backup piece 1
piece handle=/u12/data/TCMDB/bu_TCMDB_j6h3qg13 tag=TAG20051115T142918 params=NULL
channel t1: restore complete
channel t1: starting datafile backupset restore
channel t1: specifying datafile(s) to restore from backup set
restoring datafile 00016 to /u09/oracle/newdbdata/sdeskx01.dbf
channel t1: restored backup piece 1
piece handle=/u12/data/TCMDB/bu_TCMDB_j7h3qg14 tag=TAG20051115T142918 params=NULL
channel t1: restore complete
Finished restore at 15-NOV-05
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "NEWDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 64
MAXLOGMEMBERS 4
MAXDATAFILES 256
MAXINSTANCES 1
MAXLOGHISTORY 453
LOGFILE
GROUP 1 ( '/u09/oracle/newdbdata/log1a.dbf', '/u11/oracle/newdbdata/log1b.dbf' ) SIZE 10485760 REUSE,
GROUP 2 ( '/u09/oracle/newdbdata/log2a.dbf', '/u11/oracle/newdbdata/log2b.dbf' ) SIZE 10485760 REUSE
DATAFILE
'/u09/oracle/newdbdata/system01.dbf'
CHARACTER SET UTF8
printing stored script: Memory Script
{
switch clone datafile all;
}
executing script: Memory Script
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=574442499 filename=/u11/oracle/newdbdata/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=574442499 filename=/u11/oracle/newdbdata/writerd01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=574442499 filename=/u09/oracle/newdbdata/writerx01.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=574442499 filename=/u11/oracle/newdbdata/writerrepod01.dbf
datafile 6 switched to datafile copy
input datafilecopy recid=5 stamp=574442499 filename=/u09/oracle/newdbdata/writerrepox01.dbf
datafile 7 switched to datafile copy
input datafilecopy recid=6 stamp=574442499 filename=/u11/oracle/newdbdata/ovdbd01.dbf
datafile 8 switched to datafile copy
input datafilecopy recid=7 stamp=574442499 filename=/u09/oracle/newdbdata/ovdbx01.dbf
datafile 9 switched to datafile copy
input datafilecopy recid=8 stamp=574442499 filename=/u11/oracle/newdbdata/tools01.dbf
datafile 10 switched to datafile copy
input datafilecopy recid=9 stamp=574442499 filename=/u11/oracle/newdbdata/sdd01.dbf
datafile 11 switched to datafile copy
input datafilecopy recid=10 stamp=574442499 filename=/u09/oracle/newdbdata/sdx01.dbf
datafile 12 switched to datafile copy
input datafilecopy recid=11 stamp=574442499 filename=/u11/oracle/newdbdata/rdd01.dbf
datafile 13 switched to datafile copy
input datafilecopy recid=12 stamp=574442499 filename=/u09/oracle/newdbdata/rdx01.dbf
datafile 14 switched to datafile copy
input datafilecopy recid=13 stamp=574442499 filename=/u11/oracle/newdbdata/cmgmtd01.dbf
datafile 15 switched to datafile copy
input datafilecopy recid=14 stamp=574442499 filename=/u11/oracle/newdbdata/sdeskd01.dbf
datafile 16 switched to datafile copy
input datafilecopy recid=15 stamp=574442499 filename=/u09/oracle/newdbdata/sdeskx01.dbf
datafile 17 switched to datafile copy
input datafilecopy recid=16 stamp=574442499 filename=/u09/oracle/newdbdata/cmgmtx01.dbf
printing stored script: Memory Script
{
set until scn 27819646;
recover
clone database
delete archivelog
;
}
executing script: Memory Script
executing command: SET until clause
Starting recover at 15-NOV-05
starting media recovery
archive log thread 1 sequence 1 is already on disk as file /u10/oracle/testdb/9.2.0/admin/TCMDB_earth02/arch/arch_1.log
archive log filename=/u10/oracle/testdb/9.2.0/admin/TCMDB_earth02/arch/arch_1.log thread=1 sequence=1
media recovery complete
Finished recover at 15-NOV-05
printing stored script: Memory Script
{
shutdown clone;
startup clone nomount ;
}
executing script: Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 303650068 bytes
Fixed Size 455956 bytes
Variable Size 167772160 bytes
Database Buffers 134217728 bytes
Redo Buffers 1204224 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "NEWDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 64
MAXLOGMEMBERS 4
MAXDATAFILES 256
MAXINSTANCES 1
MAXLOGHISTORY 453
LOGFILE
GROUP 1 ( '/u09/oracle/newdbdata/log1a.dbf', '/u11/oracle/newdbdata/log1b.dbf' ) SIZE 10485760 REUSE,
GROUP 2 ( '/u09/oracle/newdbdata/log2a.dbf', '/u11/oracle/newdbdata/log2b.dbf' ) SIZE 10485760 REUSE
DATAFILE
'/u09/oracle/newdbdata/system01.dbf'
CHARACTER SET UTF8
printing stored script: Memory Script
{
catalog clone datafilecopy "/u11/oracle/newdbdata/undotbs01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/writerd01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/writerx01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/writerrepod01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/writerrepox01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/ovdbd01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/ovdbx01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/tools01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/sdd01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/sdx01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/rdd01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/rdx01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/cmgmtd01.dbf";
catalog clone datafilecopy "/u11/oracle/newdbdata/sdeskd01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/sdeskx01.dbf";
catalog clone datafilecopy "/u09/oracle/newdbdata/cmgmtx01.dbf";
switch clone datafile all;
}
executing script: Memory Script
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/undotbs01.dbf recid=1 stamp=574442592
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/writerd01.dbf recid=2 stamp=574442592
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/writerx01.dbf recid=3 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/writerrepod01.dbf recid=4 stamp=574442593
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/writerrepox01.dbf recid=5 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/ovdbd01.dbf recid=6 stamp=574442593
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/ovdbx01.dbf recid=7 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/tools01.dbf recid=8 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/sdd01.dbf recid=9 stamp=574442593
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/sdx01.dbf recid=10 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/rdd01.dbf recid=11 stamp=574442593
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/rdx01.dbf recid=12 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/cmgmtd01.dbf recid=13 stamp=574442593
cataloged datafile copy
datafile copy filename=/u11/oracle/newdbdata/sdeskd01.dbf recid=14 stamp=574442593
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/sdeskx01.dbf recid=15 stamp=574442593
cataloged datafile copy
datafile copy filename=/u09/oracle/newdbdata/cmgmtx01.dbf recid=16 stamp=574442593
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=574442592 filename=/u11/oracle/newdbdata/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=574442592 filename=/u11/oracle/newdbdata/writerd01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=574442593 filename=/u09/oracle/newdbdata/writerx01.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=574442593 filename=/u11/oracle/newdbdata/writerrepod01.dbf
datafile 6 switched to datafile copy
input datafilecopy recid=5 stamp=574442593 filename=/u09/oracle/newdbdata/writerrepox01.dbf
datafile 7 switched to datafile copy
input datafilecopy recid=6 stamp=574442593 filename=/u11/oracle/newdbdata/ovdbd01.dbf
datafile 8 switched to datafile copy
input datafilecopy recid=7 stamp=574442593 filename=/u09/oracle/newdbdata/ovdbx01.dbf
datafile 9 switched to datafile copy
input datafilecopy recid=8 stamp=574442593 filename=/u11/oracle/newdbdata/tools01.dbf
datafile 10 switched to datafile copy
input datafilecopy recid=9 stamp=574442593 filename=/u11/oracle/newdbdata/sdd01.dbf
datafile 11 switched to datafile copy
input datafilecopy recid=10 stamp=574442593 filename=/u09/oracle/newdbdata/sdx01.dbf
datafile 12 switched to datafile copy
input datafilecopy recid=11 stamp=574442593 filename=/u11/oracle/newdbdata/rdd01.dbf
datafile 13 switched to datafile copy
input datafilecopy recid=12 stamp=574442593 filename=/u09/oracle/newdbdata/rdx01.dbf
datafile 14 switched to datafile copy
input datafilecopy recid=13 stamp=574442593 filename=/u11/oracle/newdbdata/cmgmtd01.dbf
datafile 15 switched to datafile copy
input datafilecopy recid=14 stamp=574442593 filename=/u11/oracle/newdbdata/sdeskd01.dbf
datafile 16 switched to datafile copy
input datafilecopy recid=15 stamp=574442593 filename=/u09/oracle/newdbdata/sdeskx01.dbf
datafile 17 switched to datafile copy
input datafilecopy recid=16 stamp=574442593 filename=/u09/oracle/newdbdata/cmgmtx01.dbf
printing stored script: Memory Script
{
Alter clone database open resetlogs;
}
executing script: Memory Script
database opened
Finished Duplicate Db at 15-NOV-05
released channel: d1
Recovery Manager complete.
Don't forget to create a temp tablespace
What Move Order source types are available?
There are three Move Order source types:
A. Move Order Requisition
Generated by:
Manually generated request inside Inventory
Navigation Inventory->Transactions->Move Orders
The requisition is a manually generated request for a Move Order. May optionally utilize the approval processing - the requisition can optionally go through an Oracle Workflow approval process before it becomes a Move Order. If no approval process is used, the requisition becomes a move order immediately.
B. Replenishment Move Order
Generated by:
Kanban Cards when pull sequence calls for subinventory transfer (intra-org Kanbans)
Min Max Planning Report planned at the Subinventory Level
Replenishment Counts
Replenishment Move Orders are pre-approved and ready to be transacted.
C. Wave Pick Move Order
Generated by:
Sales Order picking
Internal Sales Order picking
The Order Management pick release process generates move orders to bring material from its source location in Inventory to a staging location, which is defined as a subinventory. In other words, a subinventory transfer.
Wave Pick Move Orders are pre-approved and ready to transact. Pick slips can also be genThere are three Move Order source types:
A. Move Order Requisition Generated by:
1. Manually generated request inside Inventory
Navigation Inventory->Transactions->Move Orders
The requisition is a manually generated request for a Move Order. May optionally utilize the approval processing - the requisition can optionally go through an Oracle Workflow approval process before it becomes a Move Order. If no approval process is used, the requisition becomes a move order immediately.
B. Replenishment Move Order
Generated by:
1. Kanban Cards when pull sequence calls for subinventory transfer (intra-org Kanbans)
2. Min Max Planning Report planned at the Subinventory Level
3. Replenishment Counts
Replenishment Move Orders are pre-approved and ready to be transacted.
C. Wave Pick Move Order Generated by:
1. Sales Order picking
2. Internal Sales Order picking
The Order Management pick release process generates move orders to bring material from its source location in Inventory to a staging location, which is defined as a subinventory. In other words, a subinventory transfer. Wave Pick Move Orders are pre-approved and ready to transact. Pick slips can also be generated for these Move Orders from Inventory with the release of the Oracle Order Management module.
erated for these Move Orders from Inventory with the release of the Oracle Order Management module.
What is a Move Order transaction?
Move Order is a request for a subinventory transfer or an account issue also known as an account transfer. Move Orders allow planners and facility managers to request the movement of material within the warehouse or facility for replenishment, material storage relocations and quality handling, etc. For all Move Orders the final result will be one of two supported transactions: subinventory or account transfer. Subinventory transfer transactions may still be initiated without utilizing the Move Order function if desired.
Oracle EBS INVENTORY QUIZ.................. Part 1
INVENTORY QUIZ
1.Repeat any Japanese you may have learned and what does it mean?
2.When your cursor has highlighted a menu navigation choice, what two stroke key sequence will show a list of all 'executable forms'?
3.Why can't you perform a miscellaneous transaction (receipt or issue) against the item - GO GREEN BAY?
4.What are the Oracle Inventory attributes settings to correctly identify an item as a kanban item? Don't list the routine Inventory item attributes that are for normal items, i.e. stockable, transactable, etc.
5.Of the three - Discrete, Repetitive, or MRP/MPS - which never employs the usage of Kanbans?
6.What is the last time this kanban item saw transactional activity: TOMS CANNY KANBAN ITEM?
Oracle EBS INVENTORY QUIZ.................... Part 2
INVENTORY QUIZ
1.What Item has the two words GREEN BAY embedded in it?
2.What is the On Hand quantity for this item?
3.Which sub-inventory is holding this on hand quantity?
4.Can this item be built in WIP?
5.Is this item purchasable?
6.What are the digits of the second segment (account segment) of the material overhead account in the costing info tab of the organization parameters for the PET Modality?
Saturday, December 22, 2012
afmkinit.sh exiting with status 127
afmkinit.sh exiting with status 127
.end std out.
cp: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
ch: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
Skipping INSTE8_PRF
Skipping INSTE8_APPLY
AutoConfig could not successfully execute the following scripts:
afmkinit.sh INSTE8_SETUP 127
AutoConfig is exiting with status 1
Cause
For Oracle Enterprise Linux 5, Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10 , the LD_ASSUME_KERNEL environment variable should be unset before starting the installation. The installation fails when the LD_ASSUME_KERNEL variable is set by the dgetlnxver.sh file during the course of the installation.
Solution
Please apply the following workaround:
1. Open the <9i rdbms_oracle_home="rdbms_oracle_home">/appsutil/bin/adgetlnxver.sh file for edit.
2. After opening replacing all occurrences of LD_ASSUME_KERNEL with XD_ASSUME_KERNEL
3. Press the retry button in rapidwiz screen
SSL IMPLEMENTATION PLAN in ERP SYSTEM
The following picture shows a model plan for implementation of SSL in ERP System
Any https client request from client desktop to web tier will be redirected to application server host. There is a firewall between the two i.e. web and application server are in different zone and due to https protocol any credentials or data will traverse as encrypted.
Pre Configuration Requirements
To use SSL in ERP System we need to fulfill the following requirements:-
1. We need a certificate and an Oracle wallet for each of our application and web server.
2. If admin decides to authenticate the clients, the clients will need certificates as well.
3. We need to configure Oracle Application Server components
4. SSL is resource-intensive. So in case of heavy SSL traffic, we should consider getting an SSL accelerator
Steps to perform
The below are the steps that are needed to be follow to implement SSL in ERP System.
All this steps has to be performed once for each of the application and web server in ERP System
1. Create a wallet
2. Create a Certificate Request (CSR)
3. Submit the Certificate Request to a Certifying Authority
4. Import the Server Certificate to the Wallet
5. Modify the OPMN wallet
6. Update the JDK Cacerts File
7. Update the Context File
8. Run Autoconfig
9. Restart the middle tier services