Project and Portfolio Management Practitioners Forum
cancel

KSC Simple Respond execution command gives timeout/waiting for something to read

Highlighted
Subhac
Valued Contributor.

KSC Simple Respond execution command gives timeout/waiting for something to read

We are trying to migrate a sql update/delete scripts . KSC Simple Command is timing out without following the default timelimit which is set to 90 mins.. Below is the log file:The same error is coming for both the functions Update and Delete.can anyone help us on this?Thanks!!

 

 

Preparing for further command execution
Issuing test commands to test the readiness of the remote host to receive commands.
Sending command: echo KSC_EXIT_STATUS $? 1
waiting for something to read...
echo KSC_EXIT_STATUS $? 1
Sending command: echo KSC_EXIT_STATUS $? 2
waiting for something to read...
echo KSC_EXIT_STATUS $? 2
Sending command: echo KSC_EXIT_STATUS $? 3
waiting for something to read...
echo KSC_EXIT_STATUS $? 3
Sending command: echo KSC_EXIT_STATUS $? 4
waiting for something to read...
echo KSC_EXIT_STATUS $? 4
Sending command: echo KSC_EXIT_STATUS $? 5
waiting for something to read...
echo KSC_EXIT_STATUS $? 5
Proceeding with command execution.
KSC Simple Respond Command Failed [Thu Apr 17 02:11:27 EST 2014]


Aborting command execution.
Closing SSH2 Session
Errors occurred during command execution.

 

8 REPLIES
Utkarsh_Mishra
Acclaimed Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

Hi,

 

The following syntax is supported for ksc respond, so a prompt and response section is needed.


ksc_simple_respond "command"
ksc_simple_respond "command" "prompt 1" "response 1" ["prompt2" "response 2" … ]
ksc_simple_respond "command" -hide "prompt 1" "response 1"["prompt 2" "response 2" … ]

Secondly make sure to set all the prompts to be "$" in both source and destination environments .profile and add "$" "echo $" at the end of ksc_simple_respond command line.

Exmaple:

ksc_simple_respond "sqlplus [DEST_ENV.ENV.DB_USERNAME]@[DEST_ENV.ENV.DB_CONNECT_STRING] @$driver" -hide "Enter password:" "[DEST_ENV.ENV.DB_PASSWORD]" "$" "echo $"

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Subhac
Valued Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

Hi Utkarsh,

 

Thanks for sharing the information.

 

Currently we are using below command:

 

ksc_simple_respond "sqlplus [DEST_ENV.ENV.DB_USERNAME]@[DEST_ENV.ENV.DB_CONNECT_STRING] @$driver" -hide "Enter password:" "[DEST_ENV.ENV.DB_PASSWORD]".

 

and we have tried appending the "$" "echo $" at the end of the command, it is working during migration to one  instance and not working for the other instance ....

 

 

The instance to which the migration is successful was elapsed in 45 seconds(updation of 27k records) and the migration was suceessful ,but the other instance was elapsed in 2 seconds and the migration was failed.

 

Can you please suggest me a solution for this?

 

Thanks in Advance!!

 

Regards.

Jason Nichols K
Acclaimed Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

Try changing your password prompt that you are looking for to "ssword:".  This is the prompt that I've always used for sqlplus and never had issue with it processing correctly. 

Utkarsh_Mishra
Acclaimed Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

As mentioned by 

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Subhac
Valued Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

Hi Utkarsh & Jason,

 

We have tried the option suggested by Jason i.e.  replaced “ENTER PASSWORD” with “ssword”, and  appended the "$" "echo $" to the end of the command line, and it seemed to work, and completely execute the sql obeying the Time-Out Parameters, but then it failed with:

 

KNTA-10895)

echo $

Waiting for command prompt

 

I assume we need to do the second key thing like adding $ to the source and destination environments which Utkarsh sugggested us in his first post.

 

Utkarsh - Could you please elaborate us where exactly we need to add '$' ..I mean is that something we need to add in commands or in which specifc area of source and destination environments. If possible ,could you please provide an example. 

 

 

Hopefully this should solve our issue:)

 

 

Regards.

 

Jason Nichols K
Acclaimed Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

Try removing the "$" "echo $" part from the command.  I've never had to use it and the only times I've had issues with sqlplus executions has been when the script didn't tell sqlplus to quit.

Subhac
Valued Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

Hi Jason,

 

I tried the option you suggested :

 

ksc_simple_respond "sqlplus [DEST_ENV.ENV.DB_USERNAME]@[DEST_ENV.ENV.DB_CONNECT_STRING] @$driver" -hide "ssword:" "[DEST_ENV.ENV.DB_PASSWORD]"

 

But still we are getting below error:

 

sqlplus apps@IREBSPSL @$driver
SQL*Plus: Release 10.1.0.5.0 - Production on Tue Apr 22 04:49:58 2014
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Enter password: ****
Waiting for command prompt
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
Enter user-name: Preparing for further command execution
Issuing test commands to test the readiness of the remote host to receive commands.
Sending command: echo KSC_EXIT_STATUS $? 1
waiting for something to read...
echo KSC_EXIT_STATUS $? 1
SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where  ::=[/][@<connect_identifier>] | /
Enter user-name: Enter user-name:
Proceeding with command execution.
KSC Simple Respond Command Failed [Mon Apr 21 22:50:01 EST 2014]


Aborting command execution.
Closing SSH2 Session
Errors occurred during command execution.
Jason Nichols K
Acclaimed Contributor.

Re: KSC Simple Respond execution command gives timeout/waiting for something to read

The real error is in the first error message block and really has nothing to do with PPM.  The Listener on your database doesn't like the connect string you are using to connect.  Essentially, it doesn't know the DB name you are trying to connect to.  For this one, you will need to rerun the Database Check on your Environment definition inside PPM to verify that you have all of the correct information entered for this environment.