09-13-2007
Pro*C Update not working from Crontab
Dear All,
I have writen a Pro*c program that does a data base select,insert,update statements and I have scheduled the program to run from crontab,
It is runing fine for the select insert and commit statement till it reaches the update statement , it throws the following error:
SQL On IPB Account 239907203 - Bill 2411212954
Oracle error, sqlstate is
Error occured. sqlcode = -3114
message = ORA-03114: not connected to ORACLE
Last SQL statement: update ipb_fix_batch_err_t e set e.STATUS=3,e.e_date=:b0 where (e.bil
At or near line number 2096
Cursor Cache Statistics
------------------------
Maximum value of MAXOPENCURSORS: 10
Maximum open cursors required: 10
Current number of open cursors: 10
Number of cache reassignments: 7
Number of SQL statement parses: 17
Number of SQL statement executions: 21
If I run the program from the command line it runs fine,
Please can any one help me in this, it is so urgent
Thanks
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I have put the following entry in crontab and it is NOT working
1 * * * * && /mybin/myjob.sh
As today is Sep 26th, Iam using NF-4 to test.
Thanks (2 Replies)
Discussion started by: baanprog
2 Replies
2. Solaris
Hi Everyone,
Each time I do update the crontab, it gets reset after exiting from the telnet session. I'm using Solaris 2.8
So it goes like this:
Step 1: Login as root, from a telnet session
Step 2: Crontab -e (I make modification)
Step 3: Save and exit
Step 4: Type crontab -l , changes... (4 Replies)
Discussion started by: Jeremy3
4 Replies
3. UNIX for Advanced & Expert Users
Dear all
We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250
i have scheduled cronjob but its not working
Crontab details
15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247
15 15 * * * mkdir -p rajesh /d4/appltest
Crontab log details
> CMD: mkdir... (4 Replies)
Discussion started by: rajesh_hv
4 Replies
4. UNIX for Dummies Questions & Answers
In /oracle folder, I created a file called "script.ksh" using vi command. The content of script.ksh is
* * * * * echo "welcome">/tmp/capture.log
I want the word "welcome" to be displayed in /tmp/capture.log file every minute.
I have created capture.log under /tmp folder.
Then in... (2 Replies)
Discussion started by: lg123
2 Replies
5. Red Hat
I can run manually script of ntopdump.sh but crontab can't run this script very five minutes.
# crontab -l
*/3 * * * * root sh /root/ping.sh
*/5 * * * * root sh /root/ntopdump.sh
#
# pwd
/root
# ls -l
total 88
-rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg
drwxrwxr-x 2 root... (14 Replies)
Discussion started by: getrue
14 Replies
6. Solaris
Shell = ksh
Hi all,
I scheduled an automated job on my application server like below,
30 13 * * 1-5 $HOME/my_script.sh
However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Discussion started by: isaacniu
6 Replies
7. HP-UX
Hi,
I have written a sample pro*c code and able compile and create a executable file without any error. But I have to run this binary in some other server by FTPing this binary to other server. The directory structure of ORACLE_HOME for both server is different. I used ORACLE_HOME as... (10 Replies)
Discussion started by: Akhirul
10 Replies
8. Linux
Hi,
I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work:
My cron is running:
UID PID PPID C STIME TTY TIME CMD
root 3755 1 0 Nov27 ? 00:00:00 crond
This... (4 Replies)
Discussion started by: krebe
4 Replies
9. Shell Programming and Scripting
Hello.
We have a big crontab file where we need to comment out for few countries and also uncomment out based on situations . Could someone let us know how this can be done using a script .
Sample file look like & here i need to comment/uncomment based on country code .
0-59 ...... (15 Replies)
Discussion started by: ron5174
15 Replies
CLOSE(7) SQL Commands CLOSE(7)
NAME
CLOSE - close a cursor
SYNOPSIS
CLOSE { name | ALL }
DESCRIPTION
CLOSE frees the resources associated with an open cursor. After the cursor is closed, no subsequent operations are allowed on it. A cursor
should be closed when it is no longer needed.
Every non-holdable open cursor is implicitly closed when a transaction is terminated by COMMIT or ROLLBACK. A holdable cursor is implicitly
closed if the transaction that created it aborts via ROLLBACK. If the creating transaction successfully commits, the holdable cursor
remains open until an explicit CLOSE is executed, or the client disconnects.
PARAMETERS
name The name of an open cursor to close.
ALL Close all open cursors.
NOTES
PostgreSQL does not have an explicit OPEN cursor statement; a cursor is considered open when it is declared. Use the DECLARE [declare(7)]
statement to declare a cursor.
You can see all available cursors by querying the pg_cursors system view.
If a cursor is closed after a savepoint which is later rolled back, the CLOSE is not rolled back; that is, the cursor remains closed.
EXAMPLES
Close the cursor liahona:
CLOSE liahona;
COMPATIBILITY
CLOSE is fully conforming with the SQL standard. CLOSE ALL is a PostgreSQL extension.
SEE ALSO
DECLARE [declare(7)], FETCH [fetch(7)], MOVE [move(7)]
SQL - Language Statements 2010-05-14 CLOSE(7)