Oracle Data: File updated on 6/18/2003 Oracle Checklist: Oracle Scripts 1) Directories: 2) Oracle connect string is DCOracle.Connect("user/password@Sid") 3) starting a listener: 4) scp howto 5) START all databases on quirinus: xxxxx relatively obsolete 6) Starting Oracle Data Bases 7) TXSI_P = /u06/app/oracle/product/815 8) TXSI_T = /u06/app/oratst/product/815 9) /u06/app/oracle/product/815/network/admin/tnsnames.ora 10) /u06/app/oratst/product/815/network/admin/tnsnames.ora 11) starting MainFrame databases: 12) stopping MainFrame databases: 13) Oracle CSI's 14) Oracle Support 15) Common oracle concept 16) python connect strings 17) finding oracle errors: 18) oracle scripts 19) starting vnc on regulus 20) creating oracle agent on a machine 21) oem 2.2 on the web 22) data gatherer 23) setting remote display. 24) move datafiles or create new files 25) Create db from scripts 26) solaris tuning tools: 27) recreating controlfiles: 28) Do not normally reorg sys tablespace: 29) Copying passwords from oracle: 30) TUNING 31) Patches to applications 32) logging on to TSTDEV 33) logging on to TSTTAX 34) importing schemas 35) finding ports using lsof 36) adding another datafile to a tablespace: 37) fixing ie browser for applications 38) modify control file to move database or datafiles 39) TKPROF AND TRACE DUMPS AND ALERT LOGS 40) Changing Passwords: 41) License Manager: 42) adadmin location: 43) Oracle view information: 44) Oracle Backups and Recovery 45) recovery scenarios: 46) Tablespace point-in-time recovery 47) Killing a session in Oracle 48) Creating XOTC schema in applications environment 49) finding the number of invalid objects in a database 50) locking in oracle 51) oracle alert log 52) Oradebug and sqlplus 53) utllockt.sql 54) oracle errors 55) create, add, rename control file 56) dropping a control file 57) creating and relocating online redo logs 58) dropping online redo log groups and members - extremely dangerous 59) adding priviledges is accomplished with the grant command 60) vcron and linuxconf 61) Oracle Patches applied 62) Finding user from pid in oracle 63) User defined environmental variables in Oracle 64) Oracle Applications Startup Scripts 65) creating a database link 66) Oracle applications table information 67) init.ora 68) alert logs and trace files 69) applying patches 70) patch failure 71) archivelog mode 72) dba_segments tells which table is in what datafile. 73) creating a tablespace 74) datafile status 75) taking a datafile offline 76) tar - untarring an individual file 77) recovery - media recovery - assumes archivelogmode is on 78) recovery - to a new mount point 79) forcing a archive switch 80) redo log restore 81) recovery types 82) forcing a flush of disk cache 83) DDL - Creates no redo log information 84) Archive Log setup 85) looking at an init.ora parameter 86) Logminer 87) creating a table from another table 88) Installing Oracle Intelligent Agent 89) Directory Structure 90) Forms, libs, report compile scripts 91) wfmailer 92) Oracle Enterprise Manager 93) oracle ftp server 94) volume manager problems with out of sync volumes 95) adrelnk.sh - relinks modules in Oracle apps 96) Oracle Stat Pack 97) Oracle printer drivers 98) Concurrent Manager Logs 97) Oracle printer drivers 98) Concurrent Manager Logs 99) Pinning in memory 100) Concurrent Managers 101) forms libraries 102) volchk - volume check 103) psrinfo - processor status 104) boot -r 105) resize a datafile (add space). 106) vnc will not start 107) adadmin/adpatch out of memory error 108) apps install: not enough tmp space 109 )adjusting TEMP space 110) WebDb :creating a developer user 111) THE SCRIPT ADUTCONF.SQL WILL PROVIDE A WEALTH OF INFORMATION 112) UNIX: automatic start and stop scripts 113) setting up autotrace. 114) Location of database files 115) Networker 116) ftp castor 117) How to change the gif on Oracle Apps. 118) Starting OEM 119) Veritos 120) Apache location 121) Inteligent agent 122) Data Gatherer 123) Resource Hog 124) Line printer status:lp 125) Printer setup 126) Apps Printers 127) Reports on the Web 128) Apps Library versions. 129) Netra 130) Webdb DAD creation 131) Starting & stopping webdb on legatus 132) finding the package version 133) rinning runInstaller.sh 134) ''Controller is not running'' error on all concurrent reports on cloned instances 135) ORA-20100: File o.tmp creation for FND_FILE failed 136) samba 137) REP-3000 internal error starting toolkit 138) Shutdown/startup the database when its saying that its can not comnnect as its shutting down 139) Gather schema statistics 140) Creating database link 141) Changing Application passwords 142) Index check in PRDHR 143) Putting the instance name on the bottom of the 1st App sign on screen 144) fndE patch problem 145) shutdown normal hangs 146) configure multiple network cards with the 8.1.7 Intelligent Agent 147) load balancing 148) Terminate Oracle processes with the UNIX kill command 149) To get the complete patch details 150) File version history report: 151) Checking Jserv 152) Dynamic SQL 153) 9i install 154) connect as sysdba 155) nfs mount 156)Open the database in readonly mode 157,EXP-00003: no storage definition found for segment(%lu, %lu) 158, http://quirinus.oktax.state.ok.us:8100/OA_HTML/jsp/fnd/aoljtest.jsp http://quirinus.oktax.state.ok.us:8500/OA_HTML/jsp/fnd/aoljtest.jsp 160, Installing and patching 11.5.7 161, problem with adconfig.sh 162) renamimg data files 163) For all product patch levels: 164) starting Org chart servr 165) Oracle9i feature Automatic Undo Management 166) Oracle password control /sge/default/oracle/access 167) global_name 168)What are the Oracle background processes/threads? 169) job que 170) Setting up OEM reporting server 171) check for concurrent manager 172)number of concurrent user session since the instance started 173) Passing parameters during mainframe put & get 174) moving AR forms 175) duplicate printer noprint causing problems 176) compilling form eg expiring system ids form 177) Problem with util file running lock box through concurrent manaers 178) Portal admin: portal/admin4otc ORCLADMIN/admin4otc 179) converting rdf file to rex file 180) LOCATION OF CFG FILES 181) Setting up printers & Installing Fonts on UNIX for Oracle Reports ====================================================================================================== 1) Directories: a) quirinus:/export/home/oracle/admin/scripts 2) Oracle connect string is DCOracle.Connect("user/password@Sid") This is of course Monty Python; 3) starting a listener: a) lsnrctl start dbname ie lsnrctl start TSTZ_T 4) scp howto a) hostname:path/file hostname:path 5) START all databases on quirinus: a) /usr/local/sbin/start_all_ora.sh Checklist One: seems to be obsolete 6) Starting Oracle Data Bases a) log into the system b) cd /usr/local/sbin c) run the script this script starts the whole oracle database environment d) starting a single database: cd to /export/home/oracle/admin/scripts dbstart -s sidname to start db e) starting a listener lsnrctl start dbname : lsnrctl start TSTZ_J 7) TXSI_P = /u06/app/oracle/product/815 8) TXSI_T = /u06/app/oratst/product/815 9) /u06/app/oracle/product/815/network/admin/tnsnames.ora 10) /u06/app/oratst/product/815/network/admin/tnsnames.ora 11) starting MainFrame databases: a) /s oratns8 <======= must be started first b) /s orampm8 <======= starts the actual db 12) stopping MainFrame databases: a) mpm8 start svrmgrl command="shutdown immediate" 13) Oracle CSI's - these do not necessary point to a particular platform a) Solaris 2452978 b) NT 2452981 c) Linux 2593693 d) MVS 2452979 14) Oracle Support a) 1-800-223-1711Oracle General Information: 15) Common oracle concept a) users - own objects --> schema b) username - is the key to access the system c) users - are granted privileges d) roles - are groups of privileges - similar to linux groups - like dba or sysadmin e) creating objects - if you can create you can drop (delete) objects f) synonyms - are alias' for a tables, views, functions (objects) 1) synonyms - may be private (only available to that user or 2) synonyms - may be public available to every user g) grants - allow users to (select, update, delete, insert) on the following objects (table, view, synonym, public synonym) in that order. h) dba views - can be seen by running the following sql: 1) select * from dba_views where view_name = 'DBA_USERS' i) sequences - a method for generating unique numbers: lots of parms 16) python connect strings - DCOracle.Connect(connect_string) connect_string = user/password@Sid i.e. DCOracle.Connect("ejenson/mypassword@TSTZ_T") look at python script getdata.py to get further info 17) finding oracle errors: oerr ora ERROR# -- ie oerr ora 947 18) oracle scripts a) /export/home/oracle/admin/scripts 19) starting vnc on regulus a) ssh -x into regulus b) su root c) cd /etc/int.d d) /usr/local/sbin/newsid ./etc/init.d/vnc stop & ./vnc start 20) creating oracle agent on a machine a) install agent from installation cd b) make sure oratab exists in /var/opt/oracle c) make sure listener.ora is not in /var/opt/oracle d) applications requires oapps.ora set correctly - currently under oracle user 1) oapps.ora is located in the following example directory a) /u05/app/oracle/product/8.1.6/network/agent/config e) start listener.ora where the agent is installed using dsmp_agent_start; may have to stop and start the dsnmp_agent 21) oem 2.2 on the web a) gecc2:3992 - This allows access to the web version of 22) data gatherer a) vppcntl - start stop ping refresh 23) setting remote display. a) xhost + remote machine i.e. xhost + limbo b) ssh -l root remote machine i.e. ssh-l root limbo c) set display on remote machine to display on local machine 1) export DISPLAY=quirinus:3 24) move datafiles or create new files a) make sure all datafiles are online --- check status in V$DATAFILES b) alter database backup controlfile to trace; c) shutdown normal - may require shutdown immediate and startup restrict first d) edit controlfile in $COMMON_TOP/admin/udump e) use reset to reuse controlfiles 1) to create new controlfiles, if needed, change reset to set f) physically move the data files 25) Create db from scripts 1) Modify create database scripts: a) scripts are found in /export/home/oratst/admin b) create directory(dbname) and copy scripts to be modified c) modify scripts for the sid name and any space and disk parameters 2) Create database files to be used by the scripts 3) Create orapwd file 4) Create network connections - tnsnames.ora and listener.ora 26) solaris tuning tools: a) /opt/RICHPse/examples 1) run ../bin/se zoom.se 2) be careful with systune can update !!! 27) recreating controlfiles: a) alter database backup controlfile to trace; b) to find trace file 1) select value from v$parameter where name = 'user_dump_dest'; 28) Do not normally reorg sys tablespace: 29) Copying passwords from oracle: a) get password using view dba_users b) user by value to save and change password 30) TUNING a) Apps Tuning - SQL b) RDBMS Tuning c) Operating System d) Init.ora - 2 parms 1) Time Statistics = True : This is good for RDBMS Tuning also 2) SQL Trace = True a) run trace file thru TKPROF: Returns an Explain Plan 1) look for full table scans b) TOAD is good for tuning SQL e) run BSTAT + ESTAT 1) Info from v$ tables : ESTAT ends and formats what BSTAT finds a) memory usage; cache hits; shared pool; dictionary; sort to disk b) v$waitstat is good c) v$sqlarea and v$sqltext = data from shared pool d) v$sess_io e) Buffer hits < 90% needs tuning dictionary hits < 90% needs tuning f) blocksize is multiple of operting system blksize g) space in extents must be contiguous !!!!!!! 31) Patches to applications a) NEVER reapply patches in oracle unless you really know what you are doing. b) Get patches from metalinks (goto patches). c) get patch by patch number or search for the patch d) Read README instructions for special instructions. e) applied patches go into appl_top/admin/instance/applptch.txt has applied patches in it. patch top is /u13/appl/applvis/PATCH f) relinks even if objects invalid g) run processes in this order: c, d, g h) patches are run from adpatch i) readme has what to run in what order. j) compile apps schema after d process, but before g process. k) use adadmin to 1) generate message files 2) recompile apps schema 3) compile flex fields 4) Menus 5) regenerate oracle java (may need to recertify java files). 32) logging on to TSTDEV a) http://quirinus:2000/OA_HTML/US/ICXINDEX.htm 33) logging on to TSTTAX b) http://quirinus:2001/OA_HTML/US/ICXINDEX.htm 34) importing schemas a) imp username/passwd@sidname fromuser=auser touser=buser 35) finding ports using lsof lsof -i tcp@: 36) adding another datafile to a tablespace: a) find the datafiles: select * from dba_data_files where tablespace_name = 'GLX'; b) add the new datafile: alter tablespace glx add datafile '/u10/oradata/DEVTAX/glx02.dbf' size 81920k; 37) fixing ie browser for applications a) log in to sqlplus as icx/icx . b) select session_cookie_domain from icx_parameters; c) update column to be .oktax.state.ok.us 38) modify control file to move database or datafiles a) make sure all datafiles are online --- check status in V$DATAFILES b) alter database backup controlfile to trace; c) shutdown normal d) edit controlfile in $COMMON_TOP/admin/udump e) use reset to reuse controlfiles 1) to create new controlfiles, if needed, change reset to set f) physically move the data files 39) TKPROF AND TRACE DUMPS AND ALERT LOGS a) alert logs are in $COMMON_TOP/admin/logs/bdump b) trace dumps are in $COMMON_TOP/admin/logs/udump c) to create a trace file in applications 1) log on to apps web page 2) select help -> diagnostics -> trace 3) after the problem process finishes turn off trace: see b above 4) go to udump directory and run TKPROF d) tkprof runs like this -> tkprof 40) Changing Passwords: a) alter user identified by ; 41) License Manager: a) licmgr is the executeable b) located in $COMMON_TOP/admin/assistants 42) adadmin location: a) $APPL_TOP/ad/11.5.0/bin 43) Oracle view information: 1) v$ views can be accessed when db in mount only 44) Oracle Backups and Recovery a) two kinds of backups 1) physical - os files 2) logical - exports b) RMAN - Recovery Manager: similar to DBRC - should backup his files also c) export - does blocklevel checking on database(checks for corruption when full export done) like pointer d) backups should consist of the following: 1) datafiles 2) controlfiles 3) rollback segments 4) online redo logs 5) archive logs 6) backup controlfile from trace - optional a) alter controlfile to trace e) two types of recovery 1) consistent recovery - recover everything to last redo log 2) inconsistent recovery - recover to a point in time, or to a SCN, or recover till cancel a) command: recover db until cancel -MUST be specified b) inconsistent recovery requires logs to be reset with the reset logs command f) recovery from loss of datafiles 1) restore datafiles from backup 2) start db in mount mode 3) apply redo logs g) these views give the os files to be backed up 1) v$datafile 2) v$logfile 3) v$controlfile h) the following sql gives location of archive logs 1) select name from V$PARAMETER where name like 'LOG_ARCH%'; i) the following views give recovery information 1) V$LOG_HISTORY - information about archived redo logs 2) V$RECOVERY_LOG - used only when database in recovery needed state by recovery manager j) imports can have redo logs applied as long as it is a tablespace, database or datafile. k) applications recovery: 1) almost always have to recover full database a) constraints are handled at the form level so database recovery is complicated see note a: l) a database must be in archivelog mode to create redo archives a) set the init.ora parameter ARCHIVELOG b) alter database statement m) LGWR process writes to current redo log and ARCH reads the most recently used redo log n) Hot backups 1) db must be in archivelog mode 2) alter tablespace begin backup - command must be issued 3) backup up tablespace files using any backup method 4) alter tablespace end backup - command must be issued o) export file limits: 1) sun solaris 2.6 is 2GIG 2) linux p) when exporting data to another os or oracle version use binary copy. 45) recovery scenarios: a) System Failure 1) recovery options a) recover whole database from cold backup (2 copies of backup recommended) b) recover whole database from hot/cold backup and apply available redo logs c) recover whole database from exports b) Disk Failure - (if not Raid1 or Raid5) 1) Make sure you have a) multiple control files b) separate devices for archive files c) multiple redo log groups 2) recovery a) restore the datafile to a new device b) rename it using the ALTER DATABASE RENAME DATAFILE command c) do recovery using archive files and online redo logs c) Database Corruption -(internal db structure is inconsistent) 1) Notes a) Usually will receive oracle error messages b) Usually can detect which database block is in error 2) Corruption Location a) Table Data 1) copy rows from non-corrupt blocks by coping them to another table. 2) drop the table 3) may have to exclude rows using unique keys or Rowids. 4) OR It may be necessary to perform datafile or database recovery b) Index 1) Drop and recreate the index c) Data Dictionary 1) options a) recover System tablespace using media recovery b) recreate Database and recover using exports d) Rollback Segments 1) If uncommitted trans perform tablespace or datafile recovery e) Data Corruption - (Db structure intact but data is not) 1) Cause a) incorrect or accidental sql statements 2) Restore Options a) restore the incorrect table/tables from most recent export. 1) Make sure referential integrity is maintained -(almost impossible with apps) b) restore the tablespace using point-in-time recovery process 1) restore to just prior to corruption 2) changes to other tables in the tablespace made after the recovery point will be lost. 3) recover the entire database to a time prior to the data corruption using hot/cold backups, archives, and redo logs. 46) Tablespace point-in-time recovery a) Description 1) SYSTEM tablespace cannot be recovered using PIT recovery 2) new in oracle 8 3) can recover one or more tablespaces to a PIT independent of other tablespaces 4) tablespaces to be recovered are refered to as the recovery set b) Process description 1) Identify objects that may be impacted by tablespace PIT and remove the objects or constraints prior to recovery a) dependent objects b) tables with reverential integrity c) indexes d) objects created after the PIT recovery time 2) Create a clone database. a) restore the datafiles to the clone using hot/cold backups 1) normally you will only need the following datafiles (for tablespace) a) SYSTEM tablespace b) rollback segments c) temporary tablespaces d) tablespace to be recovered b) Mount the database using the ALTER DATABASE MOUNT CLONE DATABASE command. c) Export the metadata about the objects in the tablespaces to be recovered d) Alter the original database to rename the datafiles to the recovered tablespace datafiles. e) Import the previous Export(c). All objects in the tablespace are effectively dropped and recreated. f) delete datafiles in the clone database 3) Limitations a) ALL tables in tablespace will be recovered - cannot recover just one table!!!! b) Must have storeage and memory to run both original and clone db's c) Any objects in recovered tablespaces created after PIT will be dropped. 4) Views a) TS_PITR_CHECK 1) Identifies objects that will be impacted by the tablespace PIT recovery 2) As long as any items are in this view PIT will fail 3) example query SELECT * FROM SYS.TS_PITR_CHECK WHERE (ts1_name IN recovery_set AND ts2_name NOT IN recovery_set) OR (ts1_name NOT IN recovery_set AND ts2_name IN recovery_set); b) TS_PITR_OBJECTS_TO_BE_DROPPED 1) Lists objects created after the tablespace PIT recovery time. 2) These objects will be dropped by recovery process 3) These objects must be copied prior to PIT recovery or they will be lost 47) Killing a session in Oracle also look at # 47, #50 , #62 & #123 a) sign in to the database where the session is running - must have proper authority sys/system b) select sid, schemaname, serial#, program from v$session; 1) this gives you the sid and serial# needed to kill session c) alter system kill session 'sid, serial#'; 1) this will kill the s,ession or open the DBA studio connect to the sid and then expand the sessions tab and get the OS Process ID then do a kill -9 from the os . 48) Creating XOTC schema in applications environment a) go to APPL_TOP and create XOTC directory with subdirectorie just like other TOP's, ie AR_TOP b) add XOTC_TOP to environment 1) go to environment file like PROD.env a) this will direct you to the adovars.env file; this is for custom information b) add the XOTC_TOP information; this will add XOTC_TOP to the list alias and etc 2) go to the applmgr home directory and there will be scripts for compiling oracle forms, reports etc 3) insure that the XOTC directories exist on the quirinus shared directory. a) this is where apps developers load the forms etc to be compiled/generated in the XOTC schema 49) finding the number of invalid objects in a database a) select count(*) from dba_objects where status = 'INVALID'; b) su - appluser login to sqlplus as system and run the recomp.sql till the number of invalid objects remains the same. Location of recomp.sql is under applusername\sidname\scripts. 50) locking in oracle also look at # 47, #50 , #62 & #123 a) unix top command my show who is locking - using resoures b) who.sql shows who is locking c) what.sql shows what is running d) dba_blockers = session_id c) dba_waiters d) catblock.sql must be run before dba_blockers and dba_waiters may be available e) apps_login.sql shows who is logged in to apps 52) Oradebug and sqlplus a) sign on to sqlplus : sqlplus /nolog b) oradebug help gives information on how to use 53) utllockt.sql - helps find information about locking problems a) found in rdbms/admin 54) oracle errors a) ora-340 - LGWR dies if it cannot write to any redo log file. Issues this error to LGWR trace file. Shutdown the db with the abort option, fix the problem, and restart the db. b) ora-346 - LGWR gets an error on a redo log file and write this error to the LGWR trace file. after 4 errors it quits writing to that file and marks it STALE in the control file. c) ora-1555 - Snapshot too old - redo log tries to wrap onto uncommitted redo records 55) create, add, rename control file a) use sqlplus /nolog to shutdown the database 1) shutdown immediate 2) startup restrict 3) shutdown normal 4) exit sqlplus b) copy an existing control file to another location. Rename if necessary. c) edit the CONTROL_FILES parameter in the INIT.ORA file and add the new control file. d) use sqlplus /nolog to restart the database 56) dropping a control file a) shutdown the database as in step 55.a b) edit the CONTROL_FILES parm and delete the old control file's name. c) restart the database d) delete the control file at the os level 57) creating and relocating online redo logs a) shutdown the database as in step 55.a b) take a complete backup of the db including logs, data files, and control files. c) using sqlplus /nolog mount the database d) rename the online redo log members e) open the database for normal operations using the command f) backup the control file since the schema of the database has changed 58) dropping online redo log groups and members - extremely dangerous a) you CANNOT drop the active redo log group b) there must be at least two redo log groups at any given time 1) IF YOU ONLY HAVE 2 THEN YOU CANNOT DROP ONE!!! c) there must be at least one member in each group available to the db. d) sql commands to drop logs and groups 1) ALTER DATABASE DROP LOGFILE MEMBER '/u01/oradata/database/redolog1.dbf'; - drops 1 member 2) ALTER DATABASE DROP LOGFILE GROUP 3; - drops an entire redo log group e) Views to manage redo log files 1) V$LOG - 2) V$LOGFILE a) status column - give the logfile status 1) STALE - shows the log member is not complete 2) INCOMPLETE - oracle cannot access the logfile 3) CURRENT or no status - the logfile is in use 3) V$THREAD 59) adding priviledges is accomplished with the grant command a) grant select any table to view_guy; 60) vcron and linuxconf a) Sun has vcron utility to set crontab parms b) Linux can use the linuxconf utility to set crontab parms.start up linuxconf and look for super user schedule event then save it and then type crontab -l 61) Oracle Patches applied a) applptch.txt located in $APPL_TOP/admin/ lists the patches applied 62) Finding user from pid in oracle also look at # 47, #50 , #62 & #123 a) sign on to application b) run /lock/who to get list of pid's and associated oracle process sid's c) run /lock/what and enter the process sid from step b; this will return the user and the process. 63) User defined environmental variables in Oracle a) these should be placed in $APPL_TOP/admin/adovars.env 64) Oracle Applications Startup Scripts a) These scripts can be found in oracle Common top/admin/scripts --> $APPLCSF/scripts as the apps owner or $ORACLE_HOME as the database user b) The Applications scripts are listed below; they should be run by the apps owner i.e. (appldev) 1) Concurrent Managers - adcmctl.sh - usage: adcmctl.sh { (APPS/APPS)} start 2) Forms Server Listener - adfroctl.sh - usage: adfroctl.sh start|stop 3) Forms Metric Server - adfmsctl.sh - usage: adfmsctl.sh start|stop 4) Forms Metric Client - adfmcctl.sh - usage: adfmcctl.sh start|stop 5) Report Review Agent - adalnctl.sh - usage: adalnctl.sh start|stop 6) Reports Server - adrepctl.sh - usage: adrepctl.sh start|stop 7) TCF SocketServer - adtcfctl.sh - usage: adtcfctl.sh start|stop 8) HTTP Server - adapcctl.sh - usage: adapcctl.sh start|stop c) The database scripts are listed below; they should be executed by database owner i.e (oradev) 1) DB Listener - addlnctl.sh - usage: addlnctl.sh start|stop 2) Database - addbctl.sh - usage: addbctl.sh start|stop immediate|normal|abort 65) creating a database link a) add the sid info into the tnsnames.ora file. eg if connecting ctltax to trntax put trntax connect string info in ctltax's tnsnames.ora file b) following the above example connect through sqlplus as xotc issue the following cmd. create database link trntax connect to xotc identified by xotctrn4otc using 'TRNTAX'; c) do a > select * from xotc_tp_forms@trntax; d) select * from DBA_DB_LINKS 1st connect as appsselect ; e) if you need to drop then > drop database link trntax 66) Oracle applications table information a) select table_name, description from applsys.fnd_tables; will give information on the tables and descriptions. 67) init.ora a) located in database home (8.1.6) - oracle user home b) must bounce db after init.ora parms are changed c) must stop concurrent manager first then stop the db in applications. 1) adcmctl.sh / stop|start --- located in $APPLCSF/scripts 2) addbctl.sh stop|start immediate|normal|abort --- located in $ORACLE_HOME/appsutils 68) alert logs and trace files a) the location of these files are defined in init.ora using the following parameters: 1) background_dump_dest 2) user_dump_dest b) normally in applications the files are located here: 1) $ORACLE_HOME/admin/bdump - oracle user home 69) applying patches a) su - application's owner (applmgr) b) shut down the concurrent managers and the webserverand form serve c) go to the patch directory - could be defined as $PATCH_TOP d) Enter the directory of the patch to be applied e) READ the README.txt !!! 1) This contains prerequisits and instructions on patch application. f) run adpatch g) adpatch log name should have the following format 1) adpatch___.log h) check log for errors. Note 70) patch failure a) run adctrl 1) this allows you to restart workers, get worker status, tell worker to quit, and etc. Note : The fnd_install_process tables exists becasue the first patch you tried installing created that table. Since you are installing a new patch you need to drop the fnd_install_process table from the applsys schema. Rerun the patch you are trying to apply and it will create the fnd_install_process table again. When adpatch runs it creates, uses, drops the fnd_install_processes table automatically. You will encounter problems if a patch fails. 71) archivelog mode a) Three init.ora settings must be changed/added to run archivelog mode as well as several optional options. 1) log_archive_start should be set to true. 2) log_archive_dest_1 ...4 should be set to the destination(s) of the archive log. a) archive_buffer_size can be added to tune archiving speed b) this naming convention requires this format: log_archive_dest_1 = (location='filename') 3) log_archive_format should be in the format log_%S.arc 4) log_archive_dest is incompatible with naming in step 2 Example Make following changes in the init.ora file log_archive_start = true # if you want automatic archiving log_archive_dest= '/u00/ora_arch/PROD' log_archive_format= arch_%S.arc [oracle@limbo oracle]$ sqlplus internal SQL*Plus: Release 8.1.6.0.0 - Production on Mon Feb 26 14:24:05 2001 (c) Copyright 1999 Oracle Corporation. All rights reserved. Connected to an idle instance. SQL> startup mount ORACLE instance started. Total System Global Area 365051888 bytes Fixed Size 69616 bytes Variable Size 322965504 bytes Database Buffers 40960000 bytes Redo Buffers 1056768 bytes Database mounted. SQL> alter database archivelog; Database altered. SQL> alter database open; Database altered. SQL> alter system switch logfile; System altered. 72) dba_segments tells which table is in what datafile. a) select segment_name, segment_type, header_file from dba_segments where segment_name = 'table_name'; b) select file_id, file_name from dba_data_files where file_id = 'header_file from above'; 73) creating a tablespace a) create tablespace 'name of tablespace' datafile 'full filename' size m default storage(initial k next k maxextents minextents 1); 74) datafile status a) select name, status from v$datafile; 75) taking a datafile offline/online a) alter database datafile 'name of file' offline; b) ALTER ROLLBACK SEGMENT "BIGROLLBACK" ONLINE 76) tar - untarring an individual file a) gtar -xvzf tarfile.tar.Z name_of_file_to_be_recovered 77) recovery - media recovery - assumes archivelogmode is on - this is for datafile/tablespace recovery a) select name from v$datafile where status = 'RECOVER'; - to get names of affected files b) ensure all affected datafiles are offline - see 75 above c) get the affected datafiles from backup - see 76 above d) recover datafile 'datafile_to_be_recovered'; - to recover datafile e) alter database datafile 'datafile' online; - to activate datafile 78) recovery - to a new mount point a) do media recovery - see 77 above b) alter database rename file 'old_file_name' to 'new_file_name'; c) recover datafile 'datafile'; 79) forcing a archive switch a) alter system switch logfile; 80) redo log restore a) must be same name b) size must be the same and reuse option must be specified 81) recovery types a) datafile, tablespace, etc 1) does not require the database to be down a) files to be recovered should be offline 2) see 77, 78 for details b) database recovery 1) backup highly recommended before recovery procedures started 2) requires the database to be in mount mode a) types of db recovery 1) complete - recovers to end of last known archive and any redo logs available 2) incomplete - recovers to some point prior to last archive log a) point-in-time - recovers to specified date/time 1) recover database until time 'yyyy-mm-dd:hh24:mi:ss'; 2) is not a secure recovery method for applications - forms do not allow for data integrity (DO NOT DO UNLESS FORCED TO BY INFORMED MANAGEMENT) b) until cancel - reads archive logs until the dba cancels the recovery 1) recover database until cancel; c) Any incomplete recovery requires the following command: 1) alter database open resetlogs; 82) forcing a flush of disk cache a) issue the following oracle command 1) alter system flush shared_pool; b) issue sync command at the os level 83) DDL - Creates no redo log information; 84) Archive Log setup a) Should be 3 groups of 2 each as a minimum b) start with 10 meg file size c) example configuration - 3 mount points; optimal would be each log on a different mount point group 1 -------- log1a ----- Disk1 log1b ----- Disk3 group 2 -------- log2a ----- Disk2 log2b ----- Disk1 group 3 -------- log3a ----- Disk3 log3b ----- Disk2 d) reference - 71 above for more information 85) looking at an init.ora parameter a) example: sql > show parameter utl_file_dir; 86) Logminer a) log on to sqlplus as sys or internal b) execute the following command to build the logminer app 1) execute dbms_logmnr_d.build( - dictionary_filename =>'dictionary.ora', - dictionary_location =>'/usr/tmp'); c) execute the following command to tell it which logfiles to process 1) execute dbms_logmnr.add_logfile ( - logfilename =>'', - options =>dbms_logmnr.new); 2) to add another logfile to logminer issue the following command a) execute dbms_logmnr.add_logfile logfilename =>'', - options => dbms_logmnr.addfile); d) to gather information about logs run the following command 1) execute dbms_logmnr.start_logmnr ( - dictfilename => '/usr/tmp/dictionary.ora'); e) data is stored in a temp file v$logmnr_contents; 1) this table exists in the current session; leave the session and its gone! 87) creating a table from another table a) this works especially well with the log_miner temp table v$logmnr_contents 1) example: create table logminer_temp as select * from V$logmnr_contents; 88) Installing Oracle Intelligent Agent also see 20 a) Install OIA into new oracle home b) insure oratab file exists in /var/opt/oracle or in /etc (linux mostly) 1) the OIA uses oratab to get oracle homes and sid names for that node - (computer) c) create user for intelligent agent 1) DO NOT!!! set $TNS_ADMIN 2) use lsnrctl to do the following: a) start ------> dbsnmp_start b) status -----> dbsnmp_status c) stop --------> dbsnmp_stop 89) Directory Structure a) application binaries 1) //app//product// b) datafiles 1) //oradata// 90) Forms, libs, report compile scripts a) location in appl owner home/scripts b) start with nohup ./gen_x_tsttax.sh & c) script names 1) gen_forms_tsttax.sh 2) gen_libs_tsttax.sh 3) gen_reports_tsttax.sh d) logs are located in /shared directory so that users may see them 91) wfmailer a) wfmailer owner is wfmailer b) scripts in /export/home/wfmailer c) wfmailer will stop when it finds a file named shutdown in it's work directory. d) su - root Password: # su - wfmailer ./check_mailer.sh ./start_mailer.sh 92) Oracle Enterprise Manager a) starting the oracle management server 1) log on as oracle 2) goto $ORACLE_HOME/bin 3) execute >>>>> oemctl start oms sysman/sysoem <<<<<< other options are stop and status b) The log is in the following directory 1) $ORACLE_HOME/sysman/log/oms.nohup c) starting the data gatherer see also 122 1) $ORACLE_HOME/bin/vppcntl -start to get the console running xon as oracle then cd $ORACLE_HOME/bin and the execute oemapp console 93) oracle ftp server a) ftp://oracle-ftp.oracle.com 94) new volume manager /opt/VRTSvmsa/bin # ./vmsa volume manager problems with out of sync volumes see also 119 a) if volumes/plexes are started they must be stopped 1) vxmend -g a5200-alpha clear all b) volumes must then be started 2) vxvol -g a5200-alpha -f start c) check the status of the volumes - insure read or writes exist 3) vxstat -g a5200-alpha -i 5 -c 5 -p OR a) if the system will not boot up at all b) insert a solaris boot cdrom disk boot up from this c) mount the root volume by eg on quirinus mount /dev/dsk/c0t0d0s0 /a d) do a touch on install-db in the /etc/vx/reconfig.d/state.d directory, VxVM will be disabled during boot.VxVM can be re-enabled during root by removing the install-db file in the /etc/vx/reconfig.d/state.d directory. e) for the oracle volumes "/u..", use the script "/usr/local/sbin/vxmender.sh" that takes care of most of what you need to do for the mirrored volumes. The plexes may have changed so kepp an eye open for those usage is eg vxmender.sh vol-10 f) here is the file /usr/local/sbin/vxmender.sh: #!/bin/sh echo FIXED.70 exit #!/bin/sh # # redo log inconsistency/NEEDSYNC # vxprint -h vol-${1} vxmend -g a5200-alpha clear all vol-${1} vxmend -g a5200-alpha clear all pl-${1}-01 pl-${1}-02 pl-${1}-03-log pl-${1}-04-log vxprint -h vol-${1} vxvol -g a5200-alpha start vol-${1} fsck -y /dev/vx/rdsk/a5200-alpha/vol-${1} mount /dev/vx/dsk/a5200-alpha/vol-${1} /u${1} 95) adrelnk.sh - relinks modules in Oracle apps a) located in AD_TOP/bin b) parms 1) force = y 2) "fnd " ie adrelnk.sh force=y "fnd xabcd" 96) Oracle Stat Pack - generates snapshots and reports on oracle system status a) located in $APPL_TOP b) user is defined is perstat/perstat c) 97) Oracle printer drivers a) located in APPL_TOP/fnd/11.5.0/reports 98) Concurrent Manager Logs a) usually located in $APPL_TOP/iem/11.5.0/log 99) Pinning in memory a) reference "Maintaining The Applications Database" 100) Concurrent Managers a) logs in $APPLCSF/log 101) forms libraries a) locations - /compile or /forms/US 1) example - $XOTC_TOP/compile or $XOTC_TOP/forms/US 102) volchk - volume check a) checks volume status 103) psrinfo - processor status a) provides information about Sun processors 104) boot -r a) this command at the sun white screen will cause the machine to check its configuration and add any new devices it finds 105) resize a datafile (add space). a) alter database datafile "filepath/name" resize 200m; 106) will not start a) ports 5900 or 6000 + preallocated probably to ssh clients b) use lsof -i tcp | grep port# to discover processes c) kill all processes using these ports d)also su - root cd /tmp cd .X11-unix rm X1 through X5 then remove logs from each users home from .vnc ,remoce server name files. the .pid & the .log d\files e) cd /etc/int.d f) ./vnc stop & ./vnc start 107) adadmin/adpatch out of memory error a) probably java memory not set high enough b) go to $APPL_TOP/admin/adovars.env c) replace the value of ADJREOPTS; current amount is mx1024m 108) apps install: not enough tmp space a) usually in /tmp b) error is signaled by an ! in the install check output c) make sure the environmental variables TMPDIR and TMP are set d) ignore the !; the installer will use TMPDIR and TMP if out of space 109 ) adjusting TEMP space a) Query the temp file. select file_name from dba_temp_files; b) alter to new size: alter database tempfile '' resize M 110) WebDb : creating a developer use CREATE USER "KGAGE" PROFILE "DEFAULT" IDENTIFIED BY "kgage" DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK; GRANT UNLIMITED TABLESPACE TO "KGAGE" GRANT "CONNECT" TO "KGAGE"; GRANT "RESOURCE" TO "KGAGE"; GRANT "WEBDB_DEVELOPER" TO "KGAGE"; 111) THE SCRIPT ADUTCONF.SQL WILL PROVIDE A WEALTH OF INFORMATION The script adutconf.sql will provide a wealth of information, including the following: Product Group(s) Multi-Org status Multi-lingual status Installed product status registered schemas Installed languages The adutconf.sql is located in $AD_TOP/11.5.0/sql, and is run via the following syntax: cd $AD_TOP/sql sqlplus apps/apps @adutconf 112) UNIX: automatic start and stop scripts su - root cd /etc/init.d copy the file that you want to use. # cp ora_lsnr_tst gen_libs_tst edit the file to your needs # vi gen_libs_tst to start a program file put a link to the file in /etc/init.d in the rc3.d # cd /etc/rc3.d ===> in linux it is /etc/rc.d/rc3.d # ln -s /etc/init.d/ora_genlibs_tst S90_2f_ora_genlibs_tst # ln -s /etc/init.d/ora_genforms_tst S90_2g_ora_genforms_tst # ln -s /etc/init.d/ora_genreports_tst S90_2h_ora_genreports_tst instead of using /etc use ../ as a relative path eg in regulus put these links in etc/rc0,d & rc1.d ln -s ../init.d/prdoem K97prdoem ln -s ../init.d/prdoem_lsnr K98prdoem_lsnr ln -s ../init.d/oem_apache K99oem_apache ln -s ../init.d/oms K99oms ln -s ../init.d/ora_ia_dg K100ora_ia_dg to start put links in etc/rc3.d # ln -s ../init.d/prdoem S97prdoem # ln -s ../init.d/prdoem_lsnr S98prdoem_lsnr # ln -s ../init.d/oem_apache S99oem_apache # ln -s ../init.d/oms S99oms # ln -s ../init.d/ora_ia_dg S100ora_ia_dg to stop the program put the link in to the file in /etc/init.d & into /etc/rc0.d 113) setting up autotrace. this creates a role which you the grant to users so that they can set autotrace on. drop role plustrace; create role plustrace; grant select on v_$sesstat to plustrace; grant select on v_$statname to plustrace; grant select on v_$session to plustrace; grant plustrace to dba with admin option; grant plustrace to SASHWORT; grant plustrace to glange; grant plustrace to RSTEPHENS; grant plustrace to PVDG; select username from dba_users; 114) Location of database files 1,database & rollback select distinct (substr(name,1,8)) from v$datafile; 2, online redo logs select * from v$logfile; 3,control files select * from v$controlfile; 4.Archive log select name,value from v$parameter where name like 'log_archive%' 115) Networker quirinus:arashid $su root Password: quirinus:arashid $cd /usr/bin/nsr # ls networker nsrwatch nwarchive nwrecover product.res save nsr.help nwadmin nwbackup nwretrieve recover # ./nwrecover & or 4074 # ./networker quirinus:arashid $su - Password: # export DISPLAY=quirinus:3 # networker & its logs are at /nsr/logs 116) ftp castor ftp castor ftpuser ----------------------userid maintence------------------password 117) How to change the gif on Oracle Apps .Look up 143 also cd /u01/u03/app/applmgr/11.5.2/common/java/oracle/apps/media file is called logo.gif rename it and replace it. On TSTAX: File /OA_HTML/US/ICXINDEX.htm (modified this file to increase the size of the screen from the default size of height=163 width=508 to a height of WIDTH 534 AND HEIGHT 284) this is measured in pixels 118) Starting OEM su - oracle/oracle start the database ---> ORACLE_HOME/bin/dbstart start the listner---> ORACLE_HOME/bin/lsnrctl start Start Mgmt Server on Unix: cd /u02/oem_204/bin oemctrl start oms oemctrl stop oms arashid/lahore 119) Veritos see also 94 arashid: su root cd /root/bin ./vxva -t & => for test version only Password: root password # export PATH=$path:/opt/vxva/bin # vxva & demo mode vxvenv a -t & 120)Apache location quirinus:appldev $pwd /u05/app/appldev/product/iAS/Apache/Apache/conf 121) Inteligent agent su - oracle . ./ORACLE.env lsnrctl help on 9i on heacte su - oracle hecate:oracle $agentctl start ps -ef | grep dbsnmp 122) Data gatherer see also 92c quirinus:oracle $cd $ORACLE_HOME cd bin /vppcntl -start ps -ef | grep vpp 123) Resource Hog also look at # 47, #50 , #62 & #123 do a top get PID log into sqlplus system/manager for the correct instance run who.sql get ORACLE_SID value run what.sql plug in oracle SID value do a kill -9 on the PID 124) Line printer status:lp lpstat -t 125 cd into /etc look at printers.conf and make sure the printer name that is defined in this file is the same name defined in the app. # more printers.conf # # If you hand edit this file, comments and structure may change. # The preferred method of modifying this file is through the use of # lpset(1M) or fncreate_printer(1M) # rm2-20_1|2nd_North-ps:\ :bsdaddr=quirinus,rm2-20_1,Solaris:\ :description=Laser in Room 2-20 #1: rm2-20_1-pcl|2nd_North-pcl:\ :bsdaddr=quirinus,rm2-20_1-pcl,Solaris: rm2-20_2|2nd_South-ps:\ :bsdaddr=quirinus,rm2-20_2,Solaris:\ :description=Laser in Room 2-20 #2: rm2-20_2-pcl|2nd_South-pcl:\ :bsdaddr=quirinus,rm2-20_2-pcl,Solaris: rmB-18_1:\ :bsdaddr=quirinus,rmB-18_1,Solaris:\ :description=InfoPrint40 in Room B-18 #1: _default:\ :use=rm2-20_1: # pwd /etc # 126) Apps Printers These has been some confusion lately on what printers are GOOD printers to choose when printing within apps. Here is what should be used: 2nd_South-pcl Second floor printer by the microwave. Use for normal pcl printing. 2nd_North-pcl Second floor printer by copier. Use for normal pcl printing. 2nd_South-ps Second floor printer by the microwave. Use for postscript printing. 2nd_North-ps Second floor printer by copier. Use for postscript printing. 127) Reports on the web, be the appl user: /u22/app/appltrn/product/iAS/Apache/Apache/conf vi apps.conf Alias /report_out/ "/u22/app/appltrn/product/11.5.3/common/admin/out/" Order allow,deny Allow from all 128) Apps Library version All the plls and plx under here. get the library names from the forms run be the functional person comparing library between two instances log on as the application user navigate to $AU_TOP/resource. then compare. /u24/app/appldev/product/11.5.3/au/11.5.0/resource strings -a ARXTWMAF.plx | grep Header and for the .pll 129) netra setup Setting up a netra.Do a nfs mount on the host of the complete product dir. /etc/dfs more dfstab share -o ro=h01.internal -d applvis_home /u00/app/applvis/product/ start the forms server and the client on the host then go over to the netra and start the client on that. eg in h01 navigate to /u00/app/applvis/product/common/admin/scripts and start script adfmcctl_h01.sh make sure both forms server and client are running on the hecate and client is running on the netra. 130) Webdb DAD creation let the user login as webdb/webdb and the go to administer listner and create a daad configure the dad in: /u01/app/oracle/product/8i/listener/cfg wdbsvr.app 131) Starting & stopping webdb on legatus cd /etc/rc.d/init.d [oracle@legatus init.d]$ su root [root@legatus init.d]# ./prdamm stop [root@legatus init.d]# ./prdamm_lsnr stop [root@legatus init.d]# ./webdb_lsnr stop [root@legatus init.d]# ./prdamm start [root@legatus init.d]# ./prdamm_lsnr start [root@legatus init.d]# ./webdb_lsnr start [root@legatus init.d]# pwd 132) finding the package version here is the statment for find a package's version: select text from dba_source where name = '(package name)' and line = 2; You can also find the version of a view with: select text from dba_views where name = '(view name)'; 133) runInstaller.sh export LD_ASSUME_KERNEL=2.2.5 134) you shut down the concurrent managers and remove ALL files from $APPLPTMP 135)ERROR ============== ERROR at line 1: ORA-20100: File o.tmp creation for FND_FILE failed. You will find more information on the cause of the error in request log. ORA-06512: at "APPS.FND_FILE", line 419 ORA-06512: at "APPS.FND_FILE", line 536 ORA-06512: at "XOTC.XOTC_ACCURE_LEAVE", line 51 ORA-06512: at line 9 SOLUTION =============== su - root cd /var/tmp ls *.tmp rm -rf *.tmp ) Samba /usr/local/samba/lib modify this file >>> smb.conf su - root /etc/init.d ./samba.server stop ./samba.server start 137) REP-3000 internal error starting toolkit make the follwing changes in the following files & bounce concurrent managers and reports server DISPLAY=quirinus:6.0 export DISPLAY in adrepctl.sh adcmctl.sh 138) Shutdown/startup the database when its saying that its can not comnnect as its shutting down a) be the correct oracle user start svrmgrl b) SVRMGR> connect internal c) !env | grep SID d) shutdown abort e) startup 139) Gather schema statistics connect as APPS user and execute the following: Use the following command to gather schema statistics: exec fnd_stats.gather_schema_statistics('ONT') < For a specific schema > exec fnd_stats.gather_schema_statistics('ALL') < For all schemas > or The concurrent program Gather Schema Statistics can be run from the System Administrator Responsibility to generate statistics. To run this program: 1. Log on to Oracle Applications with the System Administrator responsibility. 2. Navigate to the Submit Request Window which is under the Navigation List & gt; Request > Run. 3. Enter the appropriate parameters. This can be run for specific schemas by specifying the schema name or entering ¿ALL¿ to gather statistics for every schema in the database. 4. Submit the gather schema statistics program. 5. Ensure there are no other concurrent jobs running at the time, else those jobs might complete with errors. The following concurrent requests are available in Oracle Applications for gathering statistics: Analyze All Index Columns Backup Table Statistics Gather All Column Statistics <> Gather Column Statistics < Gather Schema Statistics Gather Table Statistics Restore Table Statistics 140) Creating database link eg A1 --> B1 logon to the a1 as apps a, open A1's tnsnames.ora enter B1's connect info eg B1 = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=quirinus)(PORT=1621)) (CONNECT_DATA=(SID=B1)) ) b, connect to sql as XOTC or apps. type in SQL> create database link A1ttoB1 <------------ link name connect to xotc identified by psw <-------- B1 password using 'B1'; c, select * from dba_db_links d,select * from user_db_links; <----------to get the password for the link 141) Changing Application passwords a, Connect as > sqlplus APPS/APPS & backup the current tables. SQL> create table fnd_user_bkup as select * from fnd_user; SQL> create table fnd_oracle_userid_bkup as select * from fnd_oracle_userid; b, cd $FND_TOP/bin c, run the following. FNDCPASS APPS/APPS 0 Y system/admin4otc SYSTEM APPLSYS d, cd /u06/app/applctl/product/iAS/Apache/modplsql/cfg vi wdbsvr.app and then hardcode the new pasword e, cd $FND_TOP/bin f, execute a query to extract userids and password from the database other than SYSTEM APPLSYS sqlplus APPS/APPSCTL4OTC pagesize 999 spool on pass_change.sh select 'FNDCPASS apps/APPSCTL4OTC 0 Y system/admin4otc ORACLE '|| oracle_username||' '||oracle_username||'CTL4OTC' from fnd_oracle_userid spool off g, vi pass_change.sh remove the lines for apps applsys. chmod u+x pass_change.sh h, run pass_change.sh 142) changing global database name a. What is a global database name? ---------------------------------- The global database name is the unique name of the database. In a distributed database system (a set of databases stored on multiple computers that typically appears to applications as a single database) the global database names ensure that each database is distinct from all other databases in the system. Oracle forms a database’s global database name by prefixing the database’s network domain with the individual database’s name. For example: sales.us.oracle.com and sales.uk.oracle.com The global database name defaults to DB_NAME.DB_DOMAIN and this value is marked at database creation time. If you change the DB_NAME or DB_DOMAIN after the database has been created, the value for the global database name (“GLOBAL_NAME”) will not change. b. How to determine the current global database name? A public view with the name GLOBAL_NAME is available which issues a query on the table props$. So any user can find out the global database name by querying this public view: SELECT * FROM global_name; GLOBAL_NAME ---------------------- TEST815.CH.ORACLE.COM 1 row selected. c. How to change the global database name? ------------------------------------------ To change the global database name, issue the following command (renaming the global database name will not change the value of the DB_NAME or DB_DOMAIN parameters): ALTER DATABASE RENAME GLOBAL_NAME TO remote1.oracle.com; d. you have to recreate the database links after this. 142) Index check in PRDHR select OBJECT_NAME from dba_objects where object_name like 'PER_IMAGES_OTC%'; 143) Putting the instance name on the bottom of the 1st App sign on screen.Look up 117 a be the app user ,cd /OA_HTML/US/ b, vi ICXINDEX.htm c, enter the following CTLTEST 144) fndE patch problem cd u20/app/appltst/product/iAS/Apache/Jserv/etc vi zone.properties and change wrapper.bin.parameters=-DJTFDBCFILE=quirinus_tsttax make a copy of appsweb.cfg and the the following changes serverPort=9100 serverName=quirinus domainName=.oktax.state.ok.us MetricsServerPort=9020 ; Database Connection Parameters ; ------------------------------ userid=applsyspub/pub@trntax fndnam=apps also check jinit_ver_name=Version=1,1,8,11 jinit_mimetype=application/x-jinit-applet;version=1.1.8.11 jinit_classid=clsid:86ecb6a0-400a-11d5-b638-00c04faedb18 copy to $FND_TOP/resource and $OA_HTML/bin also run adadmin choose maintain app files and generate jar files. 145) shutdown normal hangs ps -ef|grep -i SID shows the normal background processes (smon, pmon, etc.) It also reveals that there are dbsnmp processes. These dbsnmp processes make a connection to the database, and must be terminated in order for a shutdown normal to complete You can stop the dbsnmp processes by issuing dbsnmp_stop (through lsnrctl 146)Purpose: ======== The purpose of this article is to explain the support of multiple network cards with the 8.1.7 Intelligent Agent. The article aims to explain the different configuration options available to the user. Scope & Application: ==================== This article is intended for all system administrators and DBAs. How to Configure Intelligent Agent 8.1.7 With Multiple Network Cards: ===================================================================== Starting with version 8.1.7, you can configure the Intelligent Agent (and Data Gatherer) to support multiple network cards. There are three different options available to you on how the Agent can be configured with multiple network cards. The options are: o The default option is for the Intelligent Agent to bind to the primary NIC on the machine. o You can bind the Intelligent Agent to a specific NIC on the machine. o You can bind the Intelligent Agent to all the NICs on the machine. The above options also apply to the 8.1.7 Data Gatherer. The Agent has the capability of discovering services (listeners, etc.) that are listening on an IP address/NIC that is different from the IP address/NIC being used by the Agent. When a node running an Intelligent Agent has multiple network cards, each with its own IP address, the Intelligent Agent can listen and accept incoming requests on the primary network interface, on a specific IP address, or on any of the multiple IP addresses, depending on the Intelligent Agent configuration parameters. The following sections of this document give details on how the Agent can be configured for the options outlined above. o How to bind the Intelligent Agent to a specific NIC: ---------------------------------------------------- 1. Stop the Agent running on the machine. On NT stop the Agent service and on UNIX issue the command: DBSNMP_STOP at the LSNRCTL prompt. 2. Edit the file ORACLE_HOME/network/admin/snmp_rw.ora by specifying the dbsnmp.address and dbsnmp.spawnaddress parameters to: "HOST=" Example: DBSNMP.ADDRESS = (ADDRESS=(PROTOCOL=tcp)(HOST=168.66.112.196)(PORT=1748)) DBSNMP.SPAWNADDRESS = (ADDRESS=(PROTOCOL=tcp)(HOST=168.66.112.196)(PORT=1754)) 3. Restart the Intelligent Agent. On NT start the Agent service and on UNIX issue the command: DBSNMP_START at the LSNRCTL prompt. o How to bind the Intelligent Agent to all the NICs on the machine: ----------------------------------------------------------------- 1. Stop the Agent running on the machine. On NT stop the Agent service and on UNIX issue the command: DBSNMP_STOP at the LSNRCTL prompt. 2. Edit the file ORACLE_HOME/network/admin/snmp_rw.ora by specifying the dbsnmp.address and dbsnmp.spawnaddress parameters to: "HOST=" Example: DBSNMP.ADDRESS = (ADDRESS=(PROTOCOL=tcp)(HOST=FRED)(PORT=1748)) DBSNMP.SPAWNADDRESS = (ADDRESS=(PROTOCOL=tcp)(HOST=FRED)(PORT=1754)) 3. Restart the Intelligent Agent. On NT start the Agent service and on UNIX issue the command: DBSNMP_START at the LSNRCTL prompt. o How to Configure the Data Gatherer to Use Multiple Network Cards: ----------------------------------------------------------------- In order to configure the Data Gatherer a similar setup as above is required. The parameter that needs to be changed is vpp.node_address. This parameter should be specified in the SQLNET.ORA file located in the ORACLE_HOME/network/admin directory, or the directory specified by the TNS_ADMIN environment variable. By default the Data Gatherer binds to the primary network card. To use a network card other than the primary card, set vpp.node_address to the IP address of the network card. To bind the Data Gatherer to all network cards, set vpp.node_address to the hostname. 147) load balancing start the client and server on h01 for load balancing on h01:/etc/init.d/formserv made change in appsweb.cfg to say serverName=%LeastLoadedHost% in 2 places /u00/app/applprd/product/common/html/bin <--- $OA_HTML/bin appsweb.cfg /u00/app/applprd/product/11.5.4/fnd/11.5.0/resource <---$FND_TOP/resource appsweb.cfg PRDTAX :n02 n03 n04 Forms metric server is running 148) Terminate Oracle processes with the UNIX kill command As you know, there are times when it's necessary to kill all Oracle processes or a selected set of Oracle processes. One common use of the UNIX kill command is to kill all Oracle processes when the database is "locked" and you can't enter Server Manager to gracefully stop the database. When you need to terminate an Oracle instance on a UNIX server, perform the following steps: Kill all Oracle processes associated with the ORACLE_SID. Use the ipcs -pmb command to identify all held RAM memory segments. Use the ipcrm -m command to release the RAM memory from UNIX. Non-AIX only: Use the ipcs -sa command to display held semaphores, and then use the ipcrm -s command to release the held semaphores for the instance. It's easy to create a single command to terminate all Oracle processes associated with your hung database instance. In the example below, we use the ps command to identify the Oracle processes and then use the awk utility to extract the process ID (PID) for the Oracle processes. We then pipe the process ID into the UNIX kill command. root> ps -ef|grep $ORACLE_SID| \ grep -v grep|awk '{print $2}'|xargs -i kill -9 {} After we've killed all Oracle processes, we can then check for held memory using the ipcs -pmb command and remove the memory held by the database. We start by displaying all held memory segments on the database server. root> ipcs -pmb IPC status from /dev/kmem as of Mon Sep 10 16:45:16 2001 T ID KEY MODE OWNER GROUP SEGSZ CPID LPID Shared Memory: m 24064 0x4cb0be18 --rw-r----- oracle dba 28975104 1836 23847 m 1 0x4e040002 --rw-rw-rw- root root 31008 572 572 m 2 0x411ca945 --rw-rw-rw- root root 8192 572 584 m 4611 0x0c6629c9 --rw-r----- root root 7216716 1346 23981 m 4 0x06347849 --rw-rw-rw- root root 77384 1346 1361 Here we see that the only RAM memory segment owned by Oracle is ID=24064. The following command will release this memory segment: root> ipcrm -m 24064 149) To get the complete patch details also There are two new db tables under APPS schema, AD_BUGS and AD_APPLIED_PATCHES adphrept < bug_number or ALL> \ \ \ \ \ \ \ Specify 1 or 2 or 3 for query_depth 1-> Details of patches only 2-> Details of patches and their Bug Fixes only 3-> Details of patches their Bug Fixes and Bug Actions cd $AD_TOP/patch/115/sql $ sqlplus / SQL>@adphrept 1 ALL ALL ALL ALL ALL ALL ALL ALL ALL N N N N N report.txt 150) File version history report: adfhrept \ \ \ \ \ \ Example: To get the complete file version history for admorgb.pls considering only patches applied in Dec 2000: On UNIX: $ cd $AD_TOP/patch/115/sql $ sqlplus / SQL> @adfhrept.sql admorgb.pls N 12/01/00 12/31/00 ALL ALL ALL N N N N N 151) Checking jserv http://quirinus.oktax.state.ok.us:8001/servlet/IsItWorking 152) Dynamic SQL example to move and rebuild indexes from xotcd to xotcx: connect system/psw@instance spool d:\filename select 'alter index '||owner||'.'||index_name||' rebuild tablespace xotcx online;' from dba_indexes where owner = 'XOTC' and tablespace_name = 'XOTCD' / spool off 153) 9i install To determine the amount of random access memory installed on your system, /usr/sbin/prtconf | grep "Memory size" To determine the amount of swap space currently configured in your system, /usr/sbin/swap -1 operating system version uname -a To determine if a specific patch is installed, showrev -p To check whether an operating systems package pkginfo -i os_package 154) connect as sysdba sqlplus "/ as sysdba" 155) raid PURPOSE ------- This document gives a general overview of RAID (Redundant Arrays of Inexpensive Disks), the different levels of RAID and their uses, and the use of RAID with Oracle databases. SCOPE & APPLICATION ------------------- This note is intended to provide a discussion on RAID configurations. 1. Overview of RAID configurations and Oracle --------------------------------------------- RAID-0: ------- RAID-0 offers pure disk striping. The striping allows a large file to be spread across multiple disks/controllers, providing concurrent access to data because all the controllers are working in parallel. It does not provide either data redundancy or parity protection. In fact, RAID-0 is the only RAID level focusing solely on performance. Some vendors, such as EMC, do not consider level 0 as true RAID and do not offer solutions based on it. Pure RAID-0 significantly lowers MTBF, since it is highly prone to downtime. If any disk in the array (across which Oracle files are striped) fails, the database goes down. RAID-1: ------- With RAID-1, all data is written onto two independent disks (a "disk pair") for complete data protection and redundancy. RAID-1 is also referred to as disk mirroring or disk shadowing. Data is written simultaneously to both disks to ensure that writes are almost as fast as to a single disk. During reads, the disk that is the least busy is utilized. RAID-1 is the most secure and reliable of all levels due to full 100-percent redundancy. However, the main disadvantage from a performance perspective is that every write has to be duplicated. Nevertheless, read performance is enhanced, as the read can come from either disk. RAID-1 demands a significant monetary investment to duplicate each disk; however, it provides a very high Mean time between failures (MTBF). Combining RAID levels 0 and 1 (RAID-0+1) allows data to be striped across an array, in addition to mirroring each disk in the array. RAID-0 & RAID-1: ---------------- If RAID/0 is then combined with RAID/1 (mirroring) this then provides the resilience, but at a cost of having to double the number of disk drives in the configuration. There is another benefit in some RAID/1 software implementations in that the requested data is always returned from the least busy device. This can account for a further increase in performance of over 85% compared to the striped, non-mirrored configuration. Write performance on the other hand has to go to both pieces of the software mirror. If this second mirror piece is on a second controller (as would normally be recommended for controller resilience), this degradation can be as low as 4 percent. RAID-3: ------- In a RAID 3 configuration, a single drive is dedicated to storing error correction or parity data. Information is striped across the remaining drives. RAID/3 dramatically reduces the level of concurrency that the disk subsystem can support (I/O's per second) to a comparable software mirrored solution . The worst case for a system using RAID/3, would be an OLTP environment, where the number of rapid transactions is numerous and response time is critical. So to put it simply, if the environment is mainly read only (Eg Decision Support) RAID/3 provides disk redundancy with read performance slightly improved, but at the cost of write performance. Unfortunately, even decision support databases still do a significant amount of disk writing since complex joins, unique searches etc still do temporary work, thus involving disk writing. RAID-5: ------- Instead of total disk mirroring, RAID-5 computes and writes parity for every write operation. The parity disks avoid the cost of full duplication of the disk drives of RAID-1. If a disk fails, parity is used to reconstruct data without system loss. Both data and parity are spread across all the disks in the array, thus reducing disk bottleneck problems. Read performance is improved, but every write has to incur the additional overhead of reading old parity, computing new parity, writing new parity, and then writing the actual data, with the last two operations happening while two disk drives are simultaneously locked. This overhead is notorious as the RAID-5 write penalty. This write penalty can make writes significantly slower. Also, if a disk fails in a RAID-5 configuration, the I/O penalty incurred during the disk rebuild is extremely high. Read-intensive applications (DSS, data warehousing) can use RAID-5 without major real-time performance degradation (the write penalty would still be incurred during batch load operations in DSS applications). In terms of storage, however, parity constitutes a mere 20-percent overhead, compared to the 100-percent overhead in RAID-1 and 0+1. Initially, when RAID-5 technology was introduced, it was labeled as the cost-effective panacea for combining high availability and performance. Gradually, users realized the truth, and until about a couple of years ago, RAID-5 was being regarded as the villain in most OLTP shops. Many sites contemplated getting rid of RAID-5 and started looking at alternative solutions. RAID 0+1 gained prominence as the best OLTP solution for people who could afford it. Over the last two years, RAID-5 is making a comeback either as hardware-based RAID-5 or as enhanced RAID-7 or RAID-S implementations. However, RAID-5 evokes bad memories for too many OLTP database architects. RAID-S: ------- RAID S is EMC's implementation of RAID-5. However, it differs from pure RAID-5 in two main aspects: (1) It stripes the parity, but it does not stripe the data. (2) It incorporates an asynchronous hardware environment with a write cache. This cache is primarily a mechanism to defer writes, so that the overhead of calculating and writing parity information can be done by the system, while it is relatively less busy (and less likely to exasperate the user!). Many users of RAID-S imagine that since RAID-S is supposedly an enhanced version of RAID-5, data striping is automatic. They often wonder how they are experiencing I/O bottlenecks, in spite of all that striping. It is vital to remember that in RAID-S, striping of data is not automatic and has to be done manually via third-party disk-management software. RAID-7: ------- RAID-7 also implements a cache, controlled by a sophisticated built-in real-time operating system. Here, however, data is striped and parity is not. Instead, parity is held on one or more dedicated drives. RAID-7 is a patented architecture of Storage Computer Corporation. 2. Pro's and Cons of Implementing RAID technology ------------------------------------------------- There are benefits and disadvantages to using RAID, and those depend on the RAID level under consideration and the specific system in question. In general, RAID level 1 is most useful for systems where complete redundancy of data is a must and disk space is not an issue. For large datafiles or systems with less disk space, this RAID level may not be feasible. Writes under this level of RAID are no faster and no slower than 'usual'. For all other levels of RAID, writes will tend to be slower and reads will be faster than under 'normal' file systems. Writes will be slower the more frequently ECC's are calculated and the more complex those ECC's are. Depending on the ratio of reads to writes in your system, I/O speed may have a net increase or a net decrease. RAID can improve performance by distributing I/O, however, since the RAID controller spreads data over several physical drives and therefore no single drive is overburdened. The striping of data across physical drives has several consequences besides balancing I/O. One additional advantage is that logical files may be created which are larger that the maximum size usually supported by an operating system. There are disadvantages, as well, however. Striping means that it is no longer possible to locate a single datafile on a specific physical drive. This may cause the loss of some application tuning capabilities. Also, in Oracle's case, it can cause database recovery to be more time-consuming. If a single physical disk in a RAID array needs recovery, all the disks which are part of that logical RAID device must be involved in the recovery. One additional note is that the storage of ECC's may require up to 20% more disk space than would storage of data alone, so there is some disk overhead involved with usage of RAID. 3. RAID and Oracle ------------------ The usage of RAID is transparent to Oracle. All the features specific to RAID configuration are handled by the operating system and go on behind- the-scenes as far as Oracle is concerned. Different Oracle file-types are suited differently for RAID devices. Datafiles and archive logs can be placed on RAID devices, since they are accessed randomly. Redo logs should be not be put on RAID devices, since they are accessed sequentially and performance is enhanced in their case by having the disk drive head near the last write location. However, mirroring of redo log files is strongly recommended by Oracle. In terms of administration, RAID is far simple than using Oracle techniques for data placement and striping. Recommendations: In general, RAID usually impacts write operations more than read operation. This is specially true where parity need to be calculated (RAID 3, RAID 5, etc). Online or archived redo log files can be put on RAID 1 devices. You should not use RAID 5. 'TEMP' tablespace data files should also go on RAID1 instead of RAID5 as well. The reason for this is that streamed write performance of distributed parity (RAID5) isn't as good as that of simple mirroring (RAID1). Swap space can be used on RAID devices without affecting Oracle. ==================================================================================== RAID Type of RAID Control Database Redo Log Archive Log File File File File ==================================================================================== 0 Striping Avoid* OK* Avoid* Avoid* ------------------------------------------------------------------------------------- 1 Shadowing OK OK Recommended Recommended ------------------------------------------------------------------------------------- 0+1 Striping + OK Recommended Avoid Avoid Shadowing (1) ------------------------------------------------------------------------------------- 3 Striping with OK Avoid Avoid Avoid Static Parity (2) ------------------------------------------------------------------------------------- 5 Striping with OK Avoid Avoid Avoid Rotating Parity (2) ------------------------------------------------------------------------------------- * RAID 0 does not provide any protection against failures. It requires a strong backup strategy. (1) RAID 0+1 is recommended for database files because this avoids hot spots and gives the best possible performance during a disk failure. The disadvantage of RAID 0+1 is that it is a costly configuration. (2) When heavy write operation involves this datafile 155)nfs mount mkdir /u00/u01/stage9i mount -F nfs -o soft,intr,ro n03:/u00/stage9i /u00/u01/stage9i 156)Open the database in readonly mode Alter database open read only; 157,EXP-00003: no storage definition found for segment(%lu, %lu) connect as sys. script is c:\EXU8STO fix: Three options for a solution: *** **************************************************** *** Solution 1 Migrate the tablespace back to dictionary *** **************************************************** SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_FROM_LOCAL('TRY_RBS'); PL/SQL procedure successfully completed. $ exp system/manager full=Y Export: Release 8.1.6.1.0 - Production on Mon Nov 13 10:57:33 2000 (c) Copyright 1999 Oracle Corporation. All rights reserved. Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production With the Partitioning option JServer Release 105.6.246.14.0 Export done in US7ASCII character set and US7ASCII NCHAR character set - OR - *** ************************************************** *** Solution 2 Drop and recreate the rollback segments *** ************************************************** SQL> drop rollback segment TRY_RS01; Rollback segment dropped. SQL> drop rollback segment TRY_RS02; Rollback segment dropped. SQL> create rollback segment try_rs01 tablespace TRY_RBS 2 storage (minextents 5); Rollback segment created. SQL> create rollback segment try_rs02 tablespace TRY_RBS 2 storage (minextents 3); Rollback segment created. SQL> alter rollback segment TRY_RS01 online; Rollback segment altered. SQL> alter rollback segment TRY_RS02 online; Rollback segment altered. $ exp system/manager full=y -OR - *** ************************************************** *** Solution 3 Recreate the view EXU8STO *** ************************************************** Replace the view EXU8STO with the new query so that TS_TYPE does not report -1 even for a freshly created locally managed tablespace. SQL> CREATE OR REPLACE view EXU8STO 2 (ownerid, tsno, fileno, blockno, iniext, sext, 3 minext, maxext, pctinc, blocks, lists, groups, 4 extents, pcache, ts_type, tsname, isonline) 5 AS 6 SELECT s$.user#, s$.ts#, s$.file#, s$.block#, 7 s$.iniexts, s$.extsize, s$.minexts, 8 s$.maxexts, s$.extpct, s$.blocks, 9 decode(s$.lists, NULL, 1, 65535, 1, lists), 10 decode(s$.groups, NULL, 1, 65535, 1, groups), extents, 11 decode(s$.cachehint, 0,'DEFAULT', 1, 'KEEP', 2, 'RECYCLE'), 12 decode(bitand(s$.spare1,1), 1, 13 decode(bitand(ts$.flags,3),0,0,1,1,2,2, -1), 14 0, -1, -1), 15 ts$.name, decode(ts$.online$, 1, 1, 4, 1, 0) 16 FROM sys.seg$ s$, sys.ts$ ts$ 17 WHERE s$.ts# = ts$.ts#(+) ; View created.adcert.txt $APPL_TOP/admin/out $ exp system/manager full=y 158) application printer printer ques have been moved to tartaros. here is how you access the gui application. root@tartaros # mozilla and open up http://localhost:631/admin or root@tartaros # pt 160, Installing and patching 11.5.7 1, log in to quirinus 6 using root config file is under Stage11i/TRNTAX 2, Patch using /u34/app/appltrn/product/8.0.6/dev6ip10 after that run patch_relink.sh 3,copy the following look in Oracle. Applications Installing Oracle Applications Release 11i (11.5.7) May 2002 Part No. A92164-01 . Chap 5 adcert.txt $APPL_TOP/admin/out (UNIX) identitydb.obj applmgr user’s home directory adsign.txt $APPL_TOP/admin (UNIX) appltop.cer $APPL_TOP/admin (UNIX) oajinit.exe $OA_HTML in (UNIX) also copy $APPLCSF/..util/jinitiator from ctl 4, Patch to c2283092.drv 5 cd aolj_dst and run the c d & g merged files using adpatch .Nmae the logs as aoljmrg 6, bring it up 7, log in as sysadmin navigate to profils/system append / at the end of the apps web agent bring it down 161, problem with adconfig.sh cd $APPL_TOP/admin cp TSTTAX.xml.bak to TSTTAX.xml ./adconfig.sh help ./adconfig.sh contextfile=$APPL_TOP/admin/TSTTAX.xml appspass=appstst everytime adconfig is run it makes a backup of the config files under /u36/app/applctl/product/11.5.7/admin/out under the data dir. check the INSTANCE_NAME.env for export_FORM60_path 162)ORA-01113 Recover the datafile: SVRMGR> CONNECT internal SVRMGR> STARTUP MOUNT SVRMGR> RECOVER DATAFILE '' SVRMGR> ALTER DATABASE OPEN; 162) renamimg data files if databse says it needs media recovery: Recover the datafile: SVRMGR> CONNECT internal SVRMGR> STARTUP MOUNT SVRMGR> RECOVER DATAFILE ''; SVRMGR> ALTER DATABASE OPEN PURPOSE In many situations, a datafile or logfile must be renamed inside Oracle. Whereas the contents of the file remain valid, you need to define a new physical name or location for it. For example: - You want to move a database file to a different disk forr performance or maintenance reasons. - You have restored a datafile from backup, but the disk wwhere it should normally be placed has crashed and you need to relocate it to a different disk. - You have moved or renamed a datafile at operating systemm level but forgot to rename it within Oracle. At startup, you get ORA-01157 and ORA-01110. If the database is up and you try to shut it down normal or immediate, you get ORA-01116 ad ORA-01110. - You have multiple databases on the same machine and you need to rename certain database files to prevent collision and confusion. SCOPE & APPLICATION This bulletin gives instructions to: I. RENAME OR MOVE DATAFILE(S) WITH THE DATABASE OPEN II. RENAME AND OR MOVE DATAFILE(S) WITH THE DATABASE SHUT DOWN III. RENAME AND OR MOVE A LOGFILE How to Rename or Move Datafiles and Logfiles: ============================================= NOTE: To rename or relocate datafiles in the SYSTEM tablespace you must use option II, 'Renaming or Moving a Datafile with the Database Shut Down', because you cannot take the SYSTEM tablespace offline. I. RENAME OR MOVE DATAFILE(S) WITH THE DATABASE OPEN ---------------------------------------------------- Datafiles can be renamed or moved while the database is open. However, the tablespace must be made READ-ONLY. This will allow users to select from the tablespace, but prevents them from doing inserts, updates, and deletes. The amount of time the tablespace is required to be read only will depend on how large the datafile(s) are and how long it takes to copy the datafile(s) to the new location. Making the tablespace read only freezes the file header, preventing updates from being made to the file header. Since this datafile is then at a read only state, it is possible to copy the file while the database is open. To do this you must follow these steps: 1. Determine how many datafiles are associated with the tablespace. SVRMGR> SELECT FILE_NAME, STATUS FROM DBA_DATA_FILES WHERE TABLESPACE_NAME = ''; 2. Make sure that all datafiles returned have the status AVAILABLE. 3. Make the tablespace is read only. SVRMGR> ALTER TABLESPACE READ ONLY; 4. Make sure that the tablespace is defined as read only in the data dictionary. SVRMGR> SELECT TABLESPACE_NAME, STATUS FROM DBA_TABLESPACES WHERE TABLESPACE_NAME = ''; TABLESPACE_NAME STATUS ------------------------------ --------- READ ONLY 5. Copy the datafile(s) to the new location using the operating system copy command. Once the datafile(s) have been copied to the new location compare the sizes of the datafiles. Make sure that the sizes match. 6. Once the datafiles have been copied to the new location alter the tablespace offline. SVRMGR> ALTER TABLESPACE OFFLINE; * At this point the tablespace is not accessible to users. 7. Once the tablespace is offline you will need to rename the datafile(s) to the new location. This updates the entry for the datafile(s) in the controlfile. SVRMGR> ALTER DATABASE RENAME FILE '/FULL_PATH_OF_OLD_LOCATION/AND_DATAFILE_NAME.DBF' TO '/FULL_PATH_OF_NEW_LOCATION/AND_DATAFILE_NAME.DBF'; * You will need to do this for all datafiles associated with this tablespace. 8. Once the alter database statement has been processed for the datafile(s) you can bring the tablespace online. SVRMGR> ALTER TABLESPACE YOUR_TABLESPACE_NAME ONLINE; 9. After you bring the tablespace back online you can make the tablespace read/write again. SVRMGR> ALTER TABLESPACE YOUR_TABLESPACE_NAME READ WRITE; 10. You can check the status of the tablespace to make sure it is read/write. You can also verify that the controlfile has been updated by doing the following: SVRMGR> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; This will produce a readable copy of the contents of your controlfile which will be placed in your user_dump_dest directory. 11. Remove the datafile(s) from the old location at the O/S level. II. RENAME AND OR MOVE DATAFILE(S) WITH THE DATABASE SHUT DOWN --------------------------------------------------------------- 1. If the database is up, shut it down. 2. Copy the datafile to the new name/location at operating system level. 3. Mount the database. SVRMGR> STARTUP MOUNT This command will read the control file but will not mount the datafiles. 4. Rename the file inside Oracle. SVRMGR> ALTER DATABASE RENAME FILE '/FULL_PATH_OF_OLD_LOCATION/AND_DATAFILE_NAME.DBF' TO '/FULL_PATH_OF_NEW_LOCATION/AND_DATAFILE_NAME.DBF'; Do this for all the datafiles that were renamed or moved at the operating system level. 5. Open the database. SVRMGR> ALTER DATABASE OPEN; 6. Query v$dbfile to confirm that the changes made were correct. SVRMGR> SELECT * FROM V$DBFILE; 7. Remove the datafile(s) from the old location at the operating system level. III. RENAME AND OR MOVE A LOGFILE ---------------------------------- 1. Shutdown the database. 2. Copy the logfile to the new name/location at operating system level. 3. Mount the database. SVRMGR> STARTUP MOUNT 4. Rename the file. SVRMGR> ALTER DATABASE RENAME FILE '/FULL_PATH_OF_OLD_LOCATION/AND_REDO_LOG_NAME.LOG' TO '/FULL_PATH_OF_NEW_LOCATION/AND_REDO_LOG_NAME.LOG'; 5. Open the database. SVRMGR> ALTER DATABASE OPEN; 6. Remove the logfile(s) from the old location at the operating system level. 163) For all product patch levels: select patch_level from fnd_product_installations; 164) starting Org chart servr /etc/init.d/ocpd start or stop location of server /opt/OCPserver 165)Oracle9i feature Automatic Undo Management PURPOSE This bulletin explains how to use the new Oracle9i feature Automatic Undo Management (AUM) versus the Manual Undo Management related to conventional rollback segments. SCOPE & APPLICATION Oracle9i. Managing Rollback/Undo Segments in Automatic Undo Management: ============================================================= This new feature simplifies and automates the management of undo segments. DBAs have the choice to manage rollback segments as they used to do under versions Oracle7, Oracle8, and Oracle8i, or to let the RDBMS do it. There are now two modes of rollback segments management and usage: * AUTOMATIC or * MANUAL To distinguish between the two types of segments, ROLLBACK segments are called UNDO segments when AUM is enabled. In both cases, rollback/undo segments are still the only way for transactions to execute and complete. This means that in any of both methods, rollback/undo segments are present in the database and use disk space. ******************* INIT.ORA parameters ******************* 1. UNDO_MANAGEMENT can be set to AUTO if you want the RDBMS to manage undo segments automatically: - RDBMS creates them when you create a new UNDO tablespacee - RDBMS alters them ONLINE/OFFLINE when you choose a speciific UNDO tablespace - RDBMS drops them when you drop an UNDO tablespace In this case, DBAs cannot manage undo segments at all, though they still do exist as "rollback" segments. Note: Though you can create rollback segments in UNDO tablespaces, it is strongly recommended not to do it. UNDO_MANAGEMENT can be set to MANUAL if you want to keep the control on rollback segments. 2. If you decide to use AUM, you have to create at least one UNDO tablespace to store the undo segments automatically created. Even if AUM uses only one UNDO tablespace at the instance level, you can create several UNDO tablespaces. In this case, specify which UNDO tablespace is to be used: UNDO_TABLESPACE=rbs SQL> select name,value from v$parameter where name in ('undo_management','undo_tablespace'); NAME VALUE ------------------------------------ ------------------------------- undo_management AUTO undo_tablespace RBS Having several UNDO tablespaces available in the database provides the possibility to switch and use a different tablespace with specific storage parameters for different purposes of usage, such as OLTP, BATCH. ************************* UNDO Tablespaces Creation ************************* 1. You create the UNDO tablespace at database creation. (Refer to [NOTE:135053.1] How to create a database with Automatic Undo Management). 2. Or after database creation: SQL> create undo tablespace UNDO_RBS1 datafile 'undorbs1.dbf' size 100m; Tablespace created. ******************************** UNDO Tablespaces Characteristics ******************************** 1. They are locally-managed with system extent allocation: SQL> select TABLESPACE_NAME, CONTENTS, EXTENT_MANAGEMENT, ALLOCATION_TYPE, SEGMENT_SPACE_MANAGEMENT from dba_tablespaces where contents='UNDO'; TABLESPACE_NAME CONTENTS EXTENT_MAN ALLOCATIO SEGMEN ------------------------------ --------- ---------- ---------- ------ RBS UNDO LOCAL SYSTEM MANUAL UNDO_RBS1 UNDO LOCAL SYSTEM MANUAL 2. You cannot use UNDO tablespaces for other purposes than UNDO SEGMENTS and cannot do any operation on system generated undo segments: SQL> create table T (c number) tablespace undo_rbs1; create table T (c number) tablespace undo_rbs1 * ERROR at line 1: ORA-30022: Cannot create segments in undo tablespace SQL> create rollback segment undo_rs1 tablespace undo_rbs1; create rollback segment undo_rs1 tablespace undo_rbs1 * ERROR at line 1: ORA-30019: RBU Rollback Segment operation not supported in SMU mode Note: You can create rollback segments on an UNDO tablespace while the database runs in manual mode, but it is useless since these rollback segments cannot be set online when running in AUM mode. 3. Only one UNDO tablespace can be used at the instance level: => use UNDO_TABLESPACE=rbs in init.ora parameter file to set it before instance startup => or use the SQL command to change the UNDO tablespace during instance life: SQL> alter system set undo_tablespace=undo_rbs1; System altered. ************************************** Rollback Segments versus UNDO Segments ************************************** 1. When creating an UNDO tablespace, these are automatically created: * n undo segments (based on SESSIONS parameter value) * named as _SYSSMUn$ * owned by PUBLIC (usable for OPS configuration) * not manually manageable SQL> select owner,segment_name,tablespace_name from dba_rollback_segs order by 3; OWNER SEGMENT_NAME TABLESPACE_NAME ------ ------------------------------ ------------------------------- PUBLIC _SYSSMU1$ RBS PUBLIC _SYSSMU2$ RBS PUBLIC _SYSSMU3$ RBS PUBLIC _SYSSMU5$ RBS PUBLIC _SYSSMU7$ RBS PUBLIC _SYSSMU9$ RBS PUBLIC _SYSSMU10$ RBS PUBLIC _SYSSMU8$ RBS PUBLIC _SYSSMU6$ RBS PUBLIC _SYSSMU4$ RBS SYS SYSTEM SYSTEM PUBLIC _SYSSMU11$ UNDO_RBS1 PUBLIC _SYSSMU12$ UNDO_RBS1 PUBLIC _SYSSMU13$ UNDO_RBS1 PUBLIC _SYSSMU14$ UNDO_RBS1 PUBLIC _SYSSMU15$ UNDO_RBS1 PUBLIC _SYSSMU16$ UNDO_RBS1 PUBLIC _SYSSMU17$ UNDO_RBS1 PUBLIC _SYSSMU18$ UNDO_RBS1 PUBLIC _SYSSMU19$ UNDO_RBS1 PUBLIC _SYSSMU20$ UNDO_RBS1 2. If you choose to use AUM, you have no chance to manage any undo or rollback, even on an non UNDO tablespace. SQL> create public rollback segment rs1 tablespace system; create public rollback segment rs1 tablespace system * ERROR at line 1: ORA-30019: Illegal rollback Segment operation in Automatic Undo mode 3. Only undo segments of the active UNDO tablespace and the SYSTEM rollback segment are kept ONLINE. All other rollback segments and undo segments of other UNDO tablespaces are OFFLINE. Nevertheless, not all undo segments of the active UNDO tablespace are ONLINE at startup: this depends on the SESSIONS parameter. For example, if 10 undo segments exist and you startup the instance with a lower SESSIONS parameter value, the existing UNDO segments are kept but only a few of them are onlined. The OFFLINE undo segments of the active UNDO tablespace are onlined when more transactions require the use of offlined undo segments. ******************************************************* Automatic Undo Management and Real Application CLusters ******************************************************* The undo space management feature is also useful in Real Application Clusters environments. 1. All instances within Real Application Cluster environments must run in the same undo mode. 2. Set the global parameter UNDO_MANAGEMENT to AUTO in your server parameter file. If you use client-side parameter files, the setting for UNDO_MANAGEMENT must be identical in all the files. 3. Set the UNDO_TABLESPACE parameter to assign the appropriate undo tablespace to each respective instance. Each instance requires its own undo tablespace. If you do not set the UNDO_TABLESPACE parameter, each instance uses the first available undo tablespace. Remarks ------- 1. There is another undo_ init.ora parameter: UNDO_SUPPRESS_ERRORS. Use it very carefully: set to TRUE, it suppresses any error message issued when attempting manual operations while in AUTO mode. SQL> alter rollback segment "_SYSSMU1$" online; Rollback segment altered. SQL> alter rollback segment "_SYSSMU13$" offline; Rollback segment altered. SQL> alter rollback segment rs1 online; Rollback segment altered. All these statements seem to have executed the operation, but in reality did not do anything. 2. Like rollback segments dropped MANUALLY, queries that need to access the transaction undo information residing in a dropped UNDO tablespace may result in ORA-01555 "snapshot too old (rollback segment too small)" error, if the snapshot is older than the DROP-SCN of the UNDO tablespace. 166) Oracle password control /sge/default/oracle/access 167) global_name select * from global_name; You need to update the "global_name" table so that "global_name" is in the form "db_name.db_domain" (i.e., PROD.WORLD). Unfortunately, once you have this problem, you cannot just use the "ALTER DATABASE RENAME GLOBAL_NAME TO" command to rectify the situation. You must update the "global_name" table directly using the correct form for a global name (i.e. of the form: db_name.db_domain). For example: UPDATE GLOBAL_NAME SET GLOBAL_NAME = 'PROD.WORLD'; Once the global name is in the correct form, further changes can be made using the supported command: ALTER DATABASE RENAME GLOBAL_NAME TO [.db_domain]; 168)What are the Oracle background processes/threads? These are the processes (on UNIX) or the threads within a process (on NT) which manage the Oracle RDBMS. Some must always be running for the server to be available; others are optional on all platforms; and some are optional and specific to certain platforms. A = Must always be running O = Optional on all platforms P = Optional and specific to a platform DBWR (A) - the database writer LGWR (A) - the log writer PMON (A) - the process monitor SMON (A) - the system monitor CKPT (O) - the checkpoint process (or thread) ARCH (O) - the archive process (or thread) RECO (O) - the recoverer process (or thread) SNPnnn (P) - snapshot process LCKnnn (P) - inter-instance locking processes Snnn (P) - shared server process in multi-threaded server Dnnn (P) - dispatcher process in multi-threaded server WMON (P) - wakeup monitor process QMNn (P) - AQ Time Manager TRWR (P) - Trace Writer LMON (P) - Lock Manager Monitor LMD0 (P) - Lock Manager Daemon 169) job que /sge/default/jobs edit the que name and enter the job you want to submit to check the status: sge.exec qmon 170) Setting up OEM reporting server. 1) install the Management Server, a pre-configured Oracle HTTP Server is automatically installed and started and this HTTP Server serves as the reporting web server (this is the same web server as is used for browser-based Enterprise Manager). In addition, reporting functionality is also automatically installed. 2) Change the default password (oem_temp) for the REPORTS_USER administrator from the Enterprise Manager Console. 3) Run the oemctl configure rws script on the machine where the Management Server and reporting web server are installed. Prior to executing the script, ensured that the Management Server on the reporting web server machine is running. This script will prompted for information such as the reporting web server host name, port number (default is 3339), Oracle Management Server host name, and the password for the REPORTS_USER administrator. psw =REPORTS_USER 4)After configuring the Reporting Web Site, tried accessing its home page directly via the URL http://regulus.oktax.state.ok.us:3339/em/OEMGenerationServlet?reportName=EM_REPORTING_HOMEPAGE 170) trouble throwing extents The next output is not strictly tuning, but it gives you a list of all database objects that will fail when they attempt to throw their next extent due to a lack of a free extent that is of sufficient size in the same tablespace as where the object resides. If the problem happens to occur on a dictionary table, the whole database can potentially freeze, which I suppose is response related 171) check concurrent managers use the command command: ps -ef | grep FNDLIBR - for UNIX use to clean them up: kill -9 count(*) from FND_CONCURRENT_PROCESSES; read Note:105133.1 172)number of concurrent user session since the instance started connect system/ SQL> select sessions_max s_max, sessions_warning s_warning, sessions_current s_current, sessions_highwater s_high, users_max from v$license; 173) Passing parameters during mainframe put & get 1: Write the script and call it eg CUSTOM.prog Place the script under /usr/local/bin and make a link to $XOTC_TOP/bin 2: Make a symbolic link from your $XOTC_TOP/bin to $FND_TOP/bin/fndcpesr For example, if the script is called CUSTOM.prog use this: ln -s $FND_TOP/bin/fndcpesr CUSTOM This link should be named the same as your script without the .prog extension . 3: Register a concurrent program as described above, using an execution method of 'Host' Use the name of your script without the .prog extension as the name of the executable For the example above, you would use CUSTOM 4: Your script will be passed at least 4 parameters, in $1 through $4 These will be: orauser/pwd, userid, username, request_id Any other parameters you define will be passed in $5 and higher. Make sure your script returns an exit status. 174) moving AR forms location when forms are compiled $XOTC_TOP/forms/US ARXCWMAI ARXRWMAI ARXTWMAI move to $AR_TOP/forms/US/ 175) duplicate printer noprint causing problems symptom: Under the System Profile Options and query under your personal id and the profile "Printer", this gives the following error message: FRM-40735: POST-QUERY trigger raised unhandled exception ORA-01422. -------------------------------------------------------------- ORA-01422: exact fetch returns more than requested number of rows change: Applied patch 1895504 cause: Duplication in table fnd_profile_options. fix: Example code on how to check and get rid of the duplication. SQL> select profile_option_id from fnd_profile_options where 2 profile_option_name = 'PRINTER'; PROFILE_OPTION_ID ----------------- 109 SQL> select count(*) from fnd_profile_option_values where 2 profile_option_id=109; COUNT(*) ---------- 4 SQL> select application_id,level_id,level_value,level_value_application_id, profile_option_value from fnd_profile_option_values where profile_option_id=109; APPL_ID LEVEL_ID LEVEL_VALUE LEVEL_VALUE_APPL_ID PROFILE_OPTION_VALUE --------- -------- ----------- --------------------- --------------------- 0 10004 1 noprint 0 10001 0 noprint 0 10004 1013 report 0 10001 0 0 report Do the following to clear the error: SQL> create table fnd_profile_option_values_bck as select * from fnd_profile_option_values; SQL> delete from fnd_profile_option_values where application_id=0 and profile_option_id=109 and level_id=10001 and level_value=0 and level_value_application_id=0; 176) compilling form To compile a form from the UNIX command line: 1. Logon as applmgr. 2. Change directories to the forms directory where all the .fmb reside. Example: $cd $AU_TOP/forms/US *** Note: Specify the full product top path for the output_file variable. 3. Execute the following command. Example: $f60gen module=FNDSCAUS.fmb userid=APPS/APPS output_file= $FND_TOP/forms/US/FNDSCAUS.fmx module_type=form batch= no compile_all=special 177) Problem with util file running lock box through concurrent managers. make sure group has wite privalage on $APPLCSF log & out directories. 178) Portal admin: portal/admin4otc ORCLADMIN/admin4otc & for OEM ias_admin/admin4otc 179) converting rdf file to rex file 1, rwcon60 stype=RDFFILE source=OTCPPSTW.rdf dtype=REXFILE dest=/shared/reports/OTCPPSTW_dev batch=yes 2, To convert a report from rex to rdf rwcon60 stype=REXFILE source= dtype=RDFFILE dest= batch=yes 180) LOCATION OF CFG FILES. UIC450\DESKTOP\CONFIG_FILES.TXT 181) Setting up printers & Installing Fonts on UNIX for Oracle Reports 1, make links to fonts from /opt/fonts/Type1/afm to /u30/app/appldev/product/8.0.6/guicommon6/tk60/admin/AFM ln -s /opt/fonts/Type1/afm/advpnetn.afm AdvPNETn ln -s /opt/fonts/Type1/afm/advplntn.afm AdvPLNT ln -s /opt/fonts/Type1/afm/advi25d_.afm AdvI25d ln -s /opt/fonts/Type1/afm/advfim__.afm AdvFIM ln -s /opt/fonts/Type1/afm/advplntn.afm AdvPLNTn ln -s /opt/fonts/Type1/afm/advpnet_.afm AdvPNET 2, cd /u30/app/appldev/product/8.0.6/guicommon6/tk60/admin/PPD open thr printername.ppd file and in the font section enter the following just above the *?FontQuery: "save *% OTC Fonts *Font AdvPNET:Standard "(001.004)" Standard ROM *Font AdvFIM: Standard "(001.000)" Standard ROM *Font AdvI25d: Standard "(001.000)" Standard ROM *Font Advocra: Standard "(001.000)" Standard ROM *Font AdvPLNT: Standard "(001.000)" Standard ROM *Font AdvPLNTn: Standard "(001.000)" Standard ROM *Font AdvPNETn: Standard "(001.000)" Standard ROM 3, cd /u30/app/appldev/product/8.0.6/guicommon6/tk60/admin/ edit the uiprint.txt add your printers as defined on unix rm2-20_1:PostScript:2:HP North Apps:hp8000_6.ppd: rm2-20_2:PostScript:2:HP South Apps:hp8000_6.ppd: 2nd_South-ps:PostScript:2:HP South App:hp8000_6.ppd: 2nd_North-ps:PostScript:2:HP North Apps:hp8000_6.ppd: intsys:PostScript:2:Xerox DocuTech 6135:xrd61357.ppd: rmB-18_1:PostScript:2:IBM Infoprint:ibm43201.ppd: # Micra Printer # rmB-18_2:PostScript:2:IBM Infoprint Micra:ibm43201.ppd: 4,edit the uifont.ali and put your font mapping for your fonts in all the sections in this file. your printer.A utility may be used to verify if the font file has the correct syntax. Run ORACLE_HOME/bin/fontchk60 # # $Header: uifont.ali@@/main/TOOLS_DEV2K_992/19 \ # Checked in on Tue Aug 15 09:14:03 PDT 2000 by mverma \ # Copyright (c) 1999, 2000 by Oracle Corporation. All Rights Reserved. \ # $ # # # $Revision: /main/TOOLS_DEV2K_992/19 $ # # Copyright (c) Oracle Corporation 1994, 2000. # All Rights Reserved. # # DESCRIPTION: # # Each line is of the form: # # ..... = \ # ..... # # The must be the name (string/identifier) of a font face. The # , , , and may either be a numeric # value or a predefined identifier/string. For example, both US7ASCII # and 1 are valid values, and refer to the same character set. # The dimension must be an explicit size, in points. # # The following is a list of recognized names and their numeric # equivalents: # # Styles Numeric value # Plain 0 # Italic 1 # Oblique 2 # Underline 4 # Outline 8 # Shadow 16 # Inverted 32 # Overstrike 64 # Blink 128 # # Weights Numeric value # Ultralight 1 # Extralight 2 # Light 3 # Demilight 4 # Medium 5 # Demibold 6 # Bold 7 # Extrabold 8 # Ultrabold 9 # # Widths Numeric value # Ultradense 1 # Extradense 2 # Dense 3 # Semidense 4 # Normal 5 # Semiexpand 6 # Expand 7 # Extraexpand 8 # Ultraexpand 9 # # Styles may be combined; you can use plus ("+") to delimit parts of a # style. For example, # # Arial..Italic+Overstrike = Helvetica.12.Italic.Bold # # are equivalent, and either one will map any Arial that has both Italic # and Overstrike styles to a 12-point, bold, italic Helvetica font. # # All strings are case-insensitive in mapping. Font faces are likely to # be case-sensitive on lookup, depending on the platform and surface, so # care should be taken with names used on the right-hand side; but they # will be mapped case-insensitively. # # See your platform documentation for a list of all supported character # sets, and available fonts. # # # BUGS: # o Should accept a RHS ratio (e.g., "Helv = Arial.2/3"). # #=============================================================== [ Global ] # Put mappings for all surfaces here. "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from MS Windows Arial = helvetica "Courier New" = courier "Times New Roman" = times Modern = helvetica "MS Sans Serif" = helvetica "MS Serif" = times "Small Fonts" = helvetica # Mapping from Macintosh "New Century Schlbk" = "new century schoolbook" "New York" = times geneva = helvetica #=============================================================== [ Printer ] # Put mappings for all printers here. "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM #=============================================================== [ Printer:PostScript1 ] # Put mappings for PostScript level 1 printers here. # Sample Kanji font mappings ...UltraLight..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...UltraLight..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS ...ExtraLight..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...ExtraLight..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS ...Light..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...Light..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS ...DemiLight..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...DemiLight..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS .....JEUC = "GothicBBB-Medium-83pv-RKSJ-H"...Medium..JEUC .....SJIS = "GothicBBB-Medium-83pv-RKSJ-H"...Medium..SJIS "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from MS Windows Roman = palatino Script = "itc zapf chancery" FixedSys = courier System = helvetica # Mapping from Macintosh # Mapping from Motif display fixed = courier clean = times lucidatypewriter = courier lucidabright = times #=============================================================== [ Printer:PostScript2 ] # Put mappings for PostScript level 2 printers here. # Sample Kanji font mappings ...UltraLight..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...UltraLight..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS ...ExtraLight..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...ExtraLight..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS ...Light..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...Light..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS ...DemiLight..JEUC = "Ryumin-Light-83pv-RKSJ-H"...Light..JEUC ...DemiLight..SJIS = "Ryumin-Light-83pv-RKSJ-H"...Light..SJIS .....JEUC = "GothicBBB-Medium-83pv-RKSJ-H"...Medium..JEUC .....SJIS = "GothicBBB-Medium-83pv-RKSJ-H"...Medium..SJIS "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from MS Windows Roman = palatino Script = "itc zapf chancery" FixedSys = courier System = helvetica "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from Macintosh "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from Motif display fixed = courier clean = times lucidatypewriter = courier lucidabright = times "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM #=============================================================== [ Printer:PCL5 ] # Put mappings for PCL 5 printers here. helvetica = univers times = "cg times" clean = "antique olv" fixed = courier lucida = univers lucidabright = "cg times" lucidatypewriter = courier "new century schoolbook" = univers terminal = "line printer" "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM #=============================================================== [ Display ] # Put mappings for all display surfaces here. "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM #=============================================================== [ Display:Motif ] # Put mappings for Motif displays here # Fix for bug no 778937 DO NOT MOVE! Roman.....sjis = lucida.....jeuc Script.....sjis = lucidabright.....jeuc FixedSys.....sjis = fixed.....jeuc System.....sjis = lucida.....jeuc .....sjis = .....jeuc "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from MS Windows Roman = lucida Script = lucidabright FixedSys = fixed System = lucida "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM # Mapping from Macintosh "Bookman" = times "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM #=============================================================== [ Display:CM ] # Put mappings for all CM displays here. # These are DEC-specific, and may need localization *..Blink = Blinking *..Inverted+Underline.Bold = ReverseBoldUnderline *..Inverted+Underline. = UnderlineReverse *..Underline.Bold = UnderlineBold *..Inverted.Bold = ReverseBold *...Bold = Bold *..Underline = Underline *..Inverted = Reverse * = Plain # The font of last resort "Advocra" = Advocra "AdvPNETn" = AdvPNETn "AdvPNET" = AdvPNET "AdvPLNTn" = AdvPLNTn "AdvPLNT" = AdvPLNT "AdvI25d" = AdvI25d "AdvFIM" = AdvFIM 5, Bounce concurrent managers 6, make sure Montys font script is running