Useful Command for VNC
Below are some useful command for VNC server
1. Start a vncserver
Command : vncserver
You will prompted to provided the password.
2. Changing the password for VNC
Command: vncpasswd : n (e.g. vncpasswd : 1)
n- The port on which the vnc is running.
3. Killing a VNC server
Command: vncserver -kill :n (e.g. vncserver -kill :n)
n- The port on which the vnc is running.
As a good practice we should use above command to clear vnc server. Killing a OS level process will not release the lock on the vnc port which was used previously for running vnc . So next time we will not be able to start on that locked vnc port.
1. Start a vncserver
Command : vncserver
You will prompted to provided the password.
2. Changing the password for VNC
Command: vncpasswd : n (e.g. vncpasswd : 1)
n- The port on which the vnc is running.
3. Killing a VNC server
Command: vncserver -kill :n (e.g. vncserver -kill :n)
n- The port on which the vnc is running.
As a good practice we should use above command to clear vnc server. Killing a OS level process will not release the lock on the vnc port which was used previously for running vnc . So next time we will not be able to start on that locked vnc port.
Scipt to Find the Concurrent Manager for a Concurrent Program
We can use the below query to find the Manager name for a Concurrent Program
Script
SELECT fcqc.INCLUDE_FLAG,
fcqc.QUEUE_APPLICATION_ID,
fcq.USER_CONCURRENT_QUEUE_NAME,
fcp.CONCURRENT_PROGRAM_NAME
FROM APPLSYS.FND_CONCURRENT_QUEUE_CONTENT fcqc,
APPLSYS.FND_CONCURRENT_PROGRAMS fcp,
APPS.FND_CONCURRENT_QUEUES_VL fcq
WHERE type_id = fcp.concurrent_program_id
AND fcp.concurrent_program_name = '&PROGRAM_SHORT_NAME'
AND fcq.concurrent_queue_id = fcqc.concurrent_queue_id;
Script
SELECT fcqc.INCLUDE_FLAG,
fcqc.QUEUE_APPLICATION_ID,
fcq.USER_CONCURRENT_QUEUE_NAME,
fcp.CONCURRENT_PROGRAM_NAME
FROM APPLSYS.FND_CONCURRENT_QUEUE_CONTENT fcqc,
APPLSYS.FND_CONCURRENT_PROGRAMS fcp,
APPS.FND_CONCURRENT_QUEUES_VL fcq
WHERE type_id = fcp.concurrent_program_id
AND fcp.concurrent_program_name = '&PROGRAM_SHORT_NAME'
AND fcq.concurrent_queue_id = fcqc.concurrent_queue_id;
Moving Oracle Home/ Making a Duplicate Oracle Home
If we want to create/clone/move oracle home or move the oracle home then we can use the clone.pl utility provided by oracle. With the use of this utility we can create a Oracle Home with all the required patches already applied.
Utility Details
Perl Script: $ORACLE_HOME/clone/bin/clone.pl.
It accepts ORACLE HOME and ORACLE HOME NAME as parameters.
Steps
Current Oracle Home: /u01/app/oracle/db
New Oracle Home: /u02/app/oracle/db
1) Tar the current ORACLE_HOME as ‘oracle’ user or the dbuser(what ever defined)
$> cd /u01/app/oracle/db
$> tar -cvf orahome.tar *
2) Copy the tar to new ORACLE_HOME location/ new server Oracle Home location
$> cd /u02/app/oracle/db
$> tar -xvf orahome.tar
3) Execute perl clone.pl script to clone a new ORACLE HOME
Setting up the environment
export ORACLE_BASE=/u02/app/oracle
export ORACLE_HOME=/u02/app/oracle/db
export PATH=${ORACLE_HOME}/bin:$PATH
Executing the clone.pl
perl ${ORACLE_HOME}/clone/bin/clone.pl ORACLE_HOME=/u02/app/oracle/db ORACLE_HOME_NAME=OraDb10g_home2
/runInstaller -silent -clone -waitForCompletion "ORACLE_HOME=/u02/app/oracle/db" "ORACLE_HOME_NAME=DbOra10g_Home2" -noConfig -nowait
Starting Oracle Universal Installer...
No pre-requisite checks found in oraparam.ini, no system pre-requisite checks will be executed.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-07-12_12-12-09AM.
Please wait ...Oracle Universal Installer, Version 10.2.0.5.0 Production Copyright (C) 1999, 2010, Oracle. All rights reserved.
You can find a log of this install session at: /oracle/oraInventory/logs/cloneActions2013-07-12_12-12-09AM.log .................................................................................................... 100% Done. Installation in progress (Friday, July 12, 2013 12:19:30 AM EDT) ...........................................................................75% Done.
Install successful
Linking in progress (Friday, July 12, 2013 12:20:22 AM EDT) Link successful
Setup in progress (Friday, July 12, 2013 12:27:50 AM EDT) Setup successful
End of install phases.(Friday, July 12, 2013 12:28:39 AM EDT)
WARNING: The following configuration scripts need to be executed as the "root" user. #!/bin/sh #Root script to run /u02/app/oracle/db/root.sh
To execute the configuration scripts:
1. Open a terminal window
2. Log in as "root"
3. Run the scripts
The cloning of DbOra10g_Home2 was successful.
Please check '/oracle/oraInventory/logs/cloneActions2013-07-12_12-12-09AM.log' for more details.
You need to have access to run root.sh or get in touch with you UNIX admin to get it executed.
4.Make sure you check/verify the new path location in all files like tnsnames.ora,listener.ora,sqlnet.ora,ifile location and pfile intDEV.ora
Utility Details
Perl Script: $ORACLE_HOME/clone/bin/clone.pl.
It accepts ORACLE HOME and ORACLE HOME NAME as parameters.
Steps
Current Oracle Home: /u01/app/oracle/db
New Oracle Home: /u02/app/oracle/db
1) Tar the current ORACLE_HOME as ‘oracle’ user or the dbuser(what ever defined)
$> cd /u01/app/oracle/db
$> tar -cvf orahome.tar *
2) Copy the tar to new ORACLE_HOME location/ new server Oracle Home location
$> cd /u02/app/oracle/db
$> tar -xvf orahome.tar
3) Execute perl clone.pl script to clone a new ORACLE HOME
Setting up the environment
export ORACLE_BASE=/u02/app/oracle
export ORACLE_HOME=/u02/app/oracle/db
export PATH=${ORACLE_HOME}/bin:$PATH
Executing the clone.pl
perl ${ORACLE_HOME}/clone/bin/clone.pl ORACLE_HOME=/u02/app/oracle/db ORACLE_HOME_NAME=OraDb10g_home2
/runInstaller -silent -clone -waitForCompletion "ORACLE_HOME=/u02/app/oracle/db" "ORACLE_HOME_NAME=DbOra10g_Home2" -noConfig -nowait
Starting Oracle Universal Installer...
No pre-requisite checks found in oraparam.ini, no system pre-requisite checks will be executed.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-07-12_12-12-09AM.
Please wait ...Oracle Universal Installer, Version 10.2.0.5.0 Production Copyright (C) 1999, 2010, Oracle. All rights reserved.
You can find a log of this install session at: /oracle/oraInventory/logs/cloneActions2013-07-12_12-12-09AM.log .................................................................................................... 100% Done. Installation in progress (Friday, July 12, 2013 12:19:30 AM EDT) ...........................................................................75% Done.
Install successful
Linking in progress (Friday, July 12, 2013 12:20:22 AM EDT) Link successful
Setup in progress (Friday, July 12, 2013 12:27:50 AM EDT) Setup successful
End of install phases.(Friday, July 12, 2013 12:28:39 AM EDT)
WARNING: The following configuration scripts need to be executed as the "root" user. #!/bin/sh #Root script to run /u02/app/oracle/db/root.sh
To execute the configuration scripts:
1. Open a terminal window
2. Log in as "root"
3. Run the scripts
The cloning of DbOra10g_Home2 was successful.
Please check '/oracle/oraInventory/logs/cloneActions2013-07-12_12-12-09AM.log' for more details.
You need to have access to run root.sh or get in touch with you UNIX admin to get it executed.
4.Make sure you check/verify the new path location in all files like tnsnames.ora,listener.ora,sqlnet.ora,ifile location and pfile intDEV.ora
PDE-PEP006 Encoded Program unit has an unknown format
If compiling a form in Oracle Apps 11i the below error is occured
Error
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)
Forms 6.0 (Form Compiler): Release - Production
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining options
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
PDE-PEP006 Encoded Program unit has an unknown format.
The Cause and solution to this problem is ad below.
Cause
If the 6i form has been opened in higher form builder version(10g or 11g) and saved even if no changes are done. But the form header will contain a slightly different value so when compiling the with formbuilder 6 version it will throw error "PDE-PEP006 Encoded Program unit has an unknown format".
There is not backward compatibility in Oracle forms.
Solution
Try to open the 6i backup fmb in form builder 6 and save . Then try to compile the form.
REFERENCE :- PDE-PEP006 When Opening FMB, MMB or PLL in Forms Builder? (Doc ID 294958.1)
Error
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)
Forms 6.0 (Form Compiler): Release - Production
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining options
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
PDE-PEP006 Encoded Program unit has an unknown format.
The Cause and solution to this problem is ad below.
Cause
If the 6i form has been opened in higher form builder version(10g or 11g) and saved even if no changes are done. But the form header will contain a slightly different value so when compiling the with formbuilder 6 version it will throw error "PDE-PEP006 Encoded Program unit has an unknown format".
There is not backward compatibility in Oracle forms.
Solution
Try to open the 6i backup fmb in form builder 6 and save . Then try to compile the form.
REFERENCE :- PDE-PEP006 When Opening FMB, MMB or PLL in Forms Builder? (Doc ID 294958.1)
Calling SuperPutty from Command Line
Like we call putty from command line the same way we can call superputty from command line.
Steps
1. Open Command Prompt
2. Run the below command. It will launch superputty and automatically login.
| "C:\Himanshu\Personnal\SuperPutty.exe" <hostname> -l <userid> -pw <password> |
Subscribe to:
Posts
(
Atom
)
No comments :
Post a Comment