Sponsored Content
Full Discussion: How to avoid ISQL error?
Top Forums Shell Programming and Scripting How to avoid ISQL error? Post 302908046 by clx on Thursday 3rd of July 2014 06:57:18 AM
Old 07-03-2014
By default it prints the message (server errors) to STDOUT.
You can invoke the isql with --retserverror option enabled to get STDERR.

Code:
isql -Uxyz -SSYB_LOCOMOTIVE_xx -Pabc -Dlmn -w300 -o$sumOfJEOutputFile --retserverror <<EOF

---------- Post updated at 16:27 ---------- Previous update was at 16:23 ----------

Found more info from manual page:

Code:
--retserverror
Forces isql to terminate and return a failure code when it encounters a server error of severity greater than 10. 
When isql encounters this type of abnormal termination, it writes the label “Msg” together with the actual Adaptive Server error number to stderr, 
and returns a value of 2 to the calling program.
isql prints the full server error message to stdout.

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

login error because of indentation isql

The below works/usr/sybase/bin/isql -S${SERVER} -D${DB} -U${ID} -P${PASSWD} -w 250 -n <<EOF > output The below is indented but doesnt work when /usr/sybase/bin/isql -S ${SERVER} \ -D ${DB} \ -U ${ID} \ -P ${PASSWD} \ -w 250 \ -n ... (1 Reply)
Discussion started by: pinnacle
1 Replies

2. Shell Programming and Scripting

Need to avoid empty line error

Hi, Below shell script executes based on liasted data files parameters.But small problem need to avoid ,If any empty line occures in dat files it's throwing oracle error .Need to ignore empty lines (means does not ready by script).Please advice. #/bin/sh adsts=`cat... (2 Replies)
Discussion started by: krajasekhar.v
2 Replies

3. Shell Programming and Scripting

Need to capture error of sybase isql in unix

Hi Gurus, I am very new in Unix, I have 1 script, in which I am truncating the table , then BCP the data in Sybase table, and then loading the data from sybase table to sybase table. every thing is working fine, but the problem is with Error. I made some hanges in my insert statement so... (3 Replies)
Discussion started by: aksar
3 Replies

4. UNIX for Dummies Questions & Answers

Error Handling using ISQL for oracle connection in Perl

Hi Am making connection to oracle using ISQL as shown in the code. This code is just a minor part of a big code. I want to capture the error if the password/login is wrong or if connection is not made. I need to capture the error code also. Also, If such an error occurs, i need to exit out... (4 Replies)
Discussion started by: irudayaraj
4 Replies

5. Red Hat

Error while executing isql command on RHEL4

Hi, I am using RHEL4 and Oracle11g , my application requires odbc connection hence I modified ODBC.ini file and when I exceute isql commande I got the following error. isql: error while loading shared libraries: /opt/nastel/apwmq/odbc/lib/libodbc.so.1: requires glibc 2.5 or later dynamic... (1 Reply)
Discussion started by: roopalidalvi231
1 Replies

6. Red Hat

Error while executing isql command on RHEL4

Hi, I am using RHEL4 and Oracle11g , my application requires odbc connection hence I modified ODBC.ini file and when I exceute isql commande I got the following error. isql: error while loading shared libraries: /opt/nastel/apwmq/odbc/lib/libodbc.so.1: requires glibc 2.5 or later dynamic... (4 Replies)
Discussion started by: roopalidalvi231
4 Replies

7. Shell Programming and Scripting

avoid error on terminal window!

Hi Guys, I am using simple ls command to find out whether the dir exist there or not. If dir found than remove. But the problem is I don't want the error shown on the terminal window that "dir not found" on the terminal window everytime i execute it. The code I am using is: set x = `/bin/ls... (4 Replies)
Discussion started by: dixits
4 Replies

8. Shell Programming and Scripting

How to avoid error with ln command?

mkdir logs mkdir: Failed to make directory "logs"; File existsTo avoid this error i use the -p argument so it creates a folder only if it is does not exists like you see below. mkdir -p logs In the similar manner i wish to avoid this error with ln command ln -s /tmp/myfolder var ln: cannot... (4 Replies)
Discussion started by: mohtashims
4 Replies

9. Shell Programming and Scripting

Isql syntax error in UNIX script

Hello Everyone, Coming again for your help to solve the below error: In a script, i had created a temp table (Temp_table) and loaded the data in it using bcp command (performed successfully) and I wanted to move it to the preferred table (called Main_table) for further use. hence I have added... (1 Reply)
Discussion started by: Suresh
1 Replies

10. UNIX for Advanced & Expert Users

Isql and If Exist syntax error in UNIX script

Hello Everyone, Coming again for your help to solve the below error: In a script, i had created a temp table (Temp_table) and loaded the data in it using bcp command (performed successfully) and I wanted to move it to the preferred table (called Main_table) for further use. hence I have added... (7 Replies)
Discussion started by: Suresh
7 Replies
Log::Message::Simple(3) 				User Contributed Perl Documentation				   Log::Message::Simple(3)

NAME
Log::Message::Simple - Simplified interface to Log::Message SYNOPSIS
use Log::Message::Simple qw[msg error debug carp croak cluck confess]; use Log::Message::Simple qw[:STD :CARP]; ### standard reporting functionality msg( "Connecting to database", $verbose ); error( "Database connection failed: $@", $verbose ); debug( "Connection arguments were: $args", $debug ); ### standard carp functionality carp( "Wrong arguments passed: @_" ); croak( "Fatal: wrong arguments passed: @_" ); cluck( "Wrong arguments passed -- including stacktrace: @_" ); confess("Fatal: wrong arguments passed -- including stacktrace: @_" ); ### retrieve individual message my @stack = Log::Message::Simple->stack; my @stack = Log::Message::Simple->flush; ### retrieve the entire stack in printable form my $msgs = Log::Message::Simple->stack_as_string; my $trace = Log::Message::Simple->stack_as_string(1); ### redirect output local $Log::Message::Simple::MSG_FH = *STDERR; local $Log::Message::Simple::ERROR_FH = *STDERR; local $Log::Message::Simple::DEBUG_FH = *STDERR; ### force a stacktrace on error local $Log::Message::Simple::STACKTRACE_ON_ERROR = 1 DESCRIPTION
This module provides standardized logging facilities using the "Log::Message" module. FUNCTIONS
msg("message string" [,VERBOSE]) Records a message on the stack, and prints it to "STDOUT" (or actually $MSG_FH, see the "GLOBAL VARIABLES" section below), if the "VERBOSE" option is true. The "VERBOSE" option defaults to false. Exported by default, or using the ":STD" tag. debug("message string" [,VERBOSE]) Records a debug message on the stack, and prints it to "STDOUT" (or actually $DEBUG_FH, see the "GLOBAL VARIABLES" section below), if the "VERBOSE" option is true. The "VERBOSE" option defaults to false. Exported by default, or using the ":STD" tag. error("error string" [,VERBOSE]) Records an error on the stack, and prints it to "STDERR" (or actually $ERROR_FH, see the "GLOBAL VARIABLES" sections below), if the "VERBOSE" option is true. The "VERBOSE" options defaults to true. Exported by default, or using the ":STD" tag. carp(); Provides functionality equal to "Carp::carp()" while still logging to the stack. Exported by using the ":CARP" tag. croak(); Provides functionality equal to "Carp::croak()" while still logging to the stack. Exported by using the ":CARP" tag. confess(); Provides functionality equal to "Carp::confess()" while still logging to the stack. Exported by using the ":CARP" tag. cluck(); Provides functionality equal to "Carp::cluck()" while still logging to the stack. Exported by using the ":CARP" tag. CLASS METHODS
Log::Message::Simple->stack() Retrieves all the items on the stack. Since "Log::Message::Simple" is implemented using "Log::Message", consult its manpage for the function "retrieve" to see what is returned and how to use the items. Log::Message::Simple->stack_as_string([TRACE]) Returns the whole stack as a printable string. If the "TRACE" option is true all items are returned with "Carp::longmess" output, rather than just the message. "TRACE" defaults to false. Log::Message::Simple->flush() Removes all the items from the stack and returns them. Since "Log::Message::Simple" is implemented using "Log::Message", consult its manpage for the function "retrieve" to see what is returned and how to use the items. GLOBAL VARIABLES
$ERROR_FH This is the filehandle all the messages sent to "error()" are being printed. This defaults to *STDERR. $MSG_FH This is the filehandle all the messages sent to "msg()" are being printed. This default to *STDOUT. $DEBUG_FH This is the filehandle all the messages sent to "debug()" are being printed. This default to *STDOUT. $STACKTRACE_ON_ERROR If this option is set to "true", every call to "error()" will generate a stacktrace using "Carp::shortmess()". Defaults to "false" perl v5.16.3 2013-01-23 Log::Message::Simple(3)
All times are GMT -4. The time now is 05:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy