'Dataguard remote process startup failed'

Question

Hi
When I try to use the Data Guard to configure my Physical Database ( Which for testing purposes, is planned to have onthe same machind as the Primary) - gives me the error
'Dataguard remote process startup failed'
Please help me.!
Can anyone give me the details of how to create a physical standby from scratch.. considernig the fact that I am new to Oracle... I am donig it as per the documentation, but not able to start the standyby database which is on the same machine using the pfile...
Thanks
Radhika

Answer 1

Are you creating standby database using data guard manager through oracle managment server? If so, have you applied patches or not?
Here is the excerpt from metalink note : 204848.1
====
Data Guard Manager reports "Data Guard remote process startup failed." Error Dialog
Fact
Oracle Enterprise Manager Data Guard Manager 9.2.0.1.0
Symptom
"Data Guard remote process startup failed" error dialog in the Oracle
Enterprise Manager 'Create Configuration' Wizard is displayed when you
attempt to run Data Guard Manager and your environment is not setup
correctly.
Fix
Check and address the following items in the order listed.
1) Ensure the Oracle installations for both the primary and standby Oracle
Homes contain Perl.
On UNIX systems, verify this by looking in each Oracle Home for the
$ORACLE_HOME/Apache/perl/bin/perl file. On NT systems, look for the
file $ORACLE_HOME\apache\perl\5.00503\bin\mswin32-x86\perl.
If this file is present, Perl is installed; and proceed to step 2.
If not, then you must install the Perl that comes with Oracle.
Follow these steps to install Perl on both the primary and standby
Oracle Homes:
a. Run the Oracle Installer and choose the Oracle Home in question.
b. Choose the "Oracle9i Database 9.2.0.1.0" option.
c. Choose "Custom" for the installation type.
d. Under "Oracle Enterprise Manager Products 9.2.0.1.0", choose to
install the "Enterprise Manager Website 9.2.0.1.0" item.
e. Complete the install.
f. Verify that the Perl installation succeeded by checking for the
presence of the above file. If successful, proceed to step 2.
2) Ensure that all Data Guard Manager patches are installed in
the OEM installation.
These following two patches are independent of each other and must both be
installed on all versions of 9.2.0:
Patch Number 3409886 (supercedes Patch 2670975)
Patch Number 2671349
Download these patches from Oracle Support Services Website, Metalink,
http://metalink.oracle.com. Activate the "Patches" button to get the
patches Web page. Enter the Patch number and activate the "Submit"
button. The patches are listed for the Windows and Solaris operating
systems only. However, they are generic patches that will work on
other platforms.
After verifying that each patches are installed, proceed to step 3.
3) Ensure the Oracle Intelligent Agent is running on both the primary and
standby nodes.
The Agent must be running for Data Guard to function. Check it by
running agentctl status on the primary and standby nodes. If it is not
running, start it by running the command agentctl start. After verifying
that it is running on both nodes, proceed to step 4.
4) Ensure that the user specified in the primary and standby node preferred
credentials can successfully run an OEM job.
Data Guard Manager requires that OEM preferred credentials are specified
for both the primary and standby node. Furthermore, these credentials
must specify a user(s) who has read/write permissions in the primary
and standby Oracle Homes, respectively.
Note well: Databases that are on Windows NT/2000 require that the
the user(s) specified in the credentials must be granted
the "Log on as a batch job" privilege.
After checking that preferred node credentials are set correctly on both
nodes, run a test OEM job to verify that jobs are functioning properly.
Do this as follows:
a) Select the Create Job item in the OEM Console Job menu.
b) Give the job a name, select Node as the Target Type, select and
add the primary node as the target.
c) Go to the Tasks tab, select and add "Run OS Command".
d) Go to the Parameters tab and specify a simple OS command such
as ls on UNIX, or dir on NT.
e) Click Submit.
f) Once the job is finished, select the Jobs icon in the OEM Console
tree, select the History tab, and examine the Job output.
If it was successful, jobs are working and you can try the Data
Guard Create Configuration wizard again.
If the job failed, you must troubleshoot this problem and fix it
before continuing with Data Guard Manager.
5) If problems persist, obtain additional information and log a
Support Request (iTAR).
If everything in the previous steps is OK, and Data Guard Manager
continues to fail, additional information is required to diagnose the
problem. The following two items must be obtained and submitted to
Oracle Support Services:
a) OEM client tracing.
The Create Configuration wizard must be run again in trace mode.
This can be done by starting OEM from a command prompt (i.e., not
the Windows NT start menu) as follows:
oemapp trace console
Client tracing messages will appear in the command window from
which this command is run. Data Guard Manager should be started and
the Create Configuration wizard should then be run up to the point
where the error occurs. All tracing messages from Create
Configuration wizard start-up to this point should then be captured
and saved into a file.
b) Data Guard job output
The output from any failed Data Guard jobs must be captured. This
can be done as follows:
1) Select the Jobs icon in the OEM Console tree.
2) Select the History tab.
3) Double-click on the latest "DataGuardCtrlXXXX" job that has a
Failed status.
4) An Edit Job window will pop up; double-click on the Failed line
to obtain the output.
5) Put the output into a file.
If a Data Guard Manager bug is submitted, the tracing output and the
job output will be required.
====
Jaffar