# $Id: common.txt,v 1.5 2015/05/12 14:17:13 RDA Exp $ # ARCS: $Header: /home/cvs/cvs/RDA_8/src/scripting/lib/mesg/en/common.txt,v 1.5 2015/05/12 14:17:13 RDA Exp $ #------------------------------------------------------------------------------ # Bad target text #------------------------------------------------------------------------------ === BadTargets === [p] RDA detected errors in the following targets: [b] ${RUN.DISPLAY.T_TGT/VB} [p] These errors prevent the collection from being performed. The possible \ solutions are: [b] Re-run the setup to fix the target errors. [B] Re-run the collection without the ${RUN.DISPLAY.K_BAD/VT} modules. #------------------------------------------------------------------------------ # No SQL*Plus #------------------------------------------------------------------------------ === NoSqlplus === [P] SQL*Plus is required for connecting to the database. [p] Do one of the following: [b] Interrupt this script, solve the problem, and next re-run rda; or [B] Press Enter to continue this script without gathering information from \ the database. [P] If you choose to continue without database connection, some information \ will be missing and Oracle Support may request that rda be re-run. #------------------------------------------------------------------------------ # Text used after an unsuccessful connection test #------------------------------------------------------------------------------ === NoConnection === [P] The database to be analyzed (${sid}) does not appear to be accessible. [p] Do one of the following: [b] If the database is not started, then start it in another session. Press \ Enter to continue this script after the database has been started; [b] Interrupt this script, start the database or solve the connection problem, \ and next re-run rda; or [B] Press Enter to continue this script without gathering information from \ the database. [P] If you choose to continue without database connection, some information \ will be missing and Oracle Support may request that rda be re-run. #------------------------------------------------------------------------------ # Start texts #------------------------------------------------------------------------------ === Start/Windows === [p] The data collection requires an initial setup to determine which \ information should be collected. To make the setup, use the same command \ used so far: [i] rda.cmd -S [p] or [I] perl rda.pl -S [P] Selective data collection is also possible. For more details, the command \ usage can be displayed by specifying the -h option, or complete manual \ page with the -M option. [P] The "rda.cmd" and "rda.pl" commands must be used from the command line. === Start === [p] The data collection requires an initial setup to determine which \ information should be collected. To make the setup, use the same command \ used so far: [i] ./rda.pl -S [p] or [I] ./rda.sh -S [P] Using the dot ensures you execute RDA from the local directory. [P] Selective data collection is also possible. For more details, the command \ usage can be displayed by specifying the -h option, or complete manual \ page with the -M option. #------------------------------------------------------------------------------ # Texts used after the setup #------------------------------------------------------------------------------ === Setup/Windows === [P] At this point, it should be possible to collect the diagnostic \ information. sqlplus should connect to the database with the userid \ specified during the setup. [p] With the same command used so far, start the data collection: [i] rda.cmd [-v] [p] or [I] perl rda.pl [-v] [P] The -v option is optional. It allows to see the collection progression. [P] Once it has completed, the results will be packaged for sending it to \ Oracle Support, if this file was generated to assist in resolving a \ Service Request. [P] Selective data collection is also possible. For more details, the command \ usage can be displayed by specifying the -h option, or complete manual \ page with the -M option. === Setup/VMS === [P] At this point, it should be possible to collect the diagnostic \ information. sqlplus should connect to the database with the userid \ specified during the setup. [p] With the same command used so far, start the data collection: [I] @RDA "-v" [P] The "-v" option is optional. It allows to see the collection progression. [P] Once it has completed, the results will be packaged for sending it to \ Oracle Support, if this file was generated to assist in resolving a \ Service Request. [P] Selective data collection is also possible. For more details, the command \ usage can be displayed by specifying the "-h" option, or complete manual \ page with the "-M" option. === Setup === [P] At this point, it should be possible to collect the diagnostic \ information. sqlplus should connect to the database with the userid \ specified during the setup. [p] With the same command used so far, start the data collection: [i] perl rda.pl [-v] [p] or [I] ./rda.sh [-v] [P] The -v option is optional. It allows to see the collection progression. [P] Once it has completed, the results will be packaged for sending it to \ Oracle Support Services, if this file was generated to assist in resolving \ a Service Request. [P] Selective data collection is also possible. For more details, the command \ usage can be displayed by specifying the -h option, or complete manual \ page with the -M option. #------------------------------------------------------------------------------ # Texts used after report packaging #------------------------------------------------------------------------------ === Packaging/Windows === [p] You can display the reports with your browser by looking at the file: [I] ${beg} [P] If this file was generated to assist in resolving a Service Request, \ send ${arc} to Oracle Support by uploading the file via My Oracle \ Support. When sending with FTP, make sure you send it in BINARY format. [P] Note: Do not submit any health, payment card or other sensitive \ production data that requires protections greater than those specified in \ the Oracle GCS Security Practices (http://www.oracle.com/us/support/\ library/customer-support-security-practices-069170.pdf). Information on \ how to remove data from your submission is available at \ https://support.oracle.com/rs?type=doc&id=1227943.1 === Packaging/Cygwin === [p] You can display the reports with your browser by looking at the file: [I] ${beg} [P] If this file was generated to assist in resolving a Service Request, \ send ${arc} to Oracle Support by uploading the file via My Oracle \ Support. When sending with FTP, make sure you send it in BINARY format. [P] Note: Do not submit any health, payment card or other sensitive \ production data that requires protections greater than those specified in \ the Oracle GCS Security Practices (http://www.oracle.com/us/support/\ library/customer-support-security-practices-069170.pdf). Information on \ how to remove data from your submission is available at \ https://support.oracle.com/rs?type=doc&id=1227943.1 === Packaging/VMS === [p] You can review the reports by transferring the ${dat} directory structure \ to a location where you have web-browser access. Then, point your browser \ at this file to display the reports: [I] ${beg} [P] If this file was generated to assist in resolving a Service Request, \ send ${arc} to Oracle Support by uploading the file via My Oracle \ Support. When sending with FTP, make sure you send it in BINARY format. [P] Note: Do not submit any health, payment card or other sensitive \ production data that requires protections greater than those specified in \ the Oracle GCS Security Practices (http://www.oracle.com/us/support/\ library/customer-support-security-practices-069170.pdf). Information on \ how to remove data from your submission is available at \ https://support.oracle.com/rs?type=doc&id=1227943.1 === Packaging === [p] You can review the reports by transferring the ${dat} directory structure \ to a location where you have web-browser access. Then, point your browser \ at this file to display the reports: [I] ${beg} [p] Based on your server configuration, some possible alternative approaches \ are: [b] If your client computer with a browser has access to a web-shared \ directory, copy the ${ctx} directory structure to the web-shared \ directory and visit this URL: [i] http://machine:port/web_shared_directory/${beg} [p] or [b] If your client computer with a browser has FTP access to the server \ computer with the ${ctx} directory, visit this URL: [I] ftp://${RDA.T_LOGIN}@${RDA.T_HOST}/${ftp} [P] If this file was generated to assist in resolving a Service Request, \ send ${arc} to Oracle Support by uploading the file via My Oracle \ Support. When sending with FTP, make sure you send it in BINARY format. [P] Note: Do not submit any health, payment card or other sensitive \ production data that requires protections greater than those specified in \ the Oracle GCS Security Practices (http://www.oracle.com/us/support/\ library/customer-support-security-practices-069170.pdf). Information on \ how to remove data from your submission is available at \ https://support.oracle.com/rs?type=doc&id=1227943.1 #------------------------------------------------------------------------------ # Texts used in connection test module #------------------------------------------------------------------------------ === TMdb:NoOracleHome === [P] ORACLE_HOME was not specified during the setup but is required for making \ a database connection. [P] To specify it, use the same command used so far with -S BEGIN as arguments. === TMdb:NoOracleSID === [P] ORACLE_SID was not specified during the setup but is required for making \ a database connection. [P] To specify it, use the same command used so far with -S DB as arguments. === TMdb:NoSqlplus === [P] SQL*Plus is required for connecting to the database. === TMdb:ConnectionError === [P] The database to be analyzed (${sid}) does not appear to be accessible. \ Look at the previous error(s) and take appropriate action. #------------------------------------------------------------------------------ # Copyright Notice # Copyright (c) 2002, 2016, Oracle and/or its affiliates. All rights reserved. # # Trademark Notice # Oracle and Java are registered trademarks of Oracle and/or its # affiliates. Other names may be trademarks of their respective owners. #------------------------------------------------------------------------------