Search Results

I am not sure if I got the problem. Anyway, I try:

This is called redirection. echo produces output to Standard Out (stdout). It is redirected by the > and just creates the file if it does not...

I added line numbers to your code for the purposes of this discussion. Obviously, the line numbers cannot appear in the code that you run:
1 LOCK_FILE=${LOG_DIR}/${DBNAME}_MD.lock
2
3 # create...

Sorry, but I must strenuously disagree with your analysis and your rewrite of the code. If you look at the originally posted script (and my analysis of it in the message #3 in this thread) you will...

Here is the other standard way to do it, to help understand better. It has one test clause, with -o separating the two conditions in the test:
if [ ${ERR_CNT} -ne 0 -o ${ERR_CNT1} -ne 0 ]

The...

Take a look at
https://www.unix.com/shell-programming-scripting/67041-if-statement.html

What shell are you running?

Try syntax as below-

if [ ${ERR_CNT} -ne 0 ] || [ ${ERR_CNT1} -ne 0 ]

First of all it seems really strange to me that you noticed path-name expansion (globbing) inside an SQL block. Maybe I'm missing something.

But you can disable path-name expansion (globbing) by...

Not sure what you mean without seeing actual example because the '*' just tells oracle to return all columns, but try it like this:
param=

load_data_to_oracle ()
{...

I didn't pay attention to this error before!
SQL*Loader-941: Error during describe of table T1_1DAY_STG
Please check and verify if you are running SQL Loader using a DB User who has sufficient...

The ORA error: ORA-04043 suggest that the table was not created successfully. So I guess the PL/SQL procedure didn't run successfully.

In PL/SQL, use semi-colon to define the end of line of code...

Use a for loop to call the function:
for param in 1day 7day 30day CTD
do
load_data_to_oracle
done
Inside the function pass the $param as argument:
@${CREATE_STAGE_SQL} "$param"
Use first...

Try this

####Main start here####
TXP_EXT_TABLE_1DAY_SQL=ext_table_1day.sql
TXP_EXT_TABLE_7DAY_SQL=ext_table_7day.sql

for i in 1DAY 7DAY
do
TXP=$( eval echo \${TXP_EXT_TABLE_${i}_SQL} )
...

You need to provide more details on what you want. We can't assume things.

--ahamed

Lets step back from where for a moment and describe how it starts (first two loops unrolled) and how it ends (when can you tell it is done and is there anything else to do).

Stating what database and shell you are using would help, but since that info is not here...

Here's a couple of ways. First, try putting put a TRIM( ) function call (or your system's equivalent)...

What I see is that you are using a lot of variables... Are they correctly set before you execute your shellscript?
Execute it in debug mode and see what is says...

Source your file:/abc/etc/TESTDB in your script right before trying to connect to DB:
. /abc/etc/TESTDB
OR
source /abc/etc/TESTDB

vi, emacs, ex, ed, or any other editor of your choice that was intended for use on systems other than Windows.

Are you editing your scripts with Microsoft Notepad?

This will fill the file with carriage returns at the end of each line, which most shells will take as literal characters. tr -d '\r' <...

You haven't given us much to help with this, but as a wild guess I'd say you edited your script with something that adds a carriage return before the newline at the end of each line. To verify, try:...

As I understand your description, you have no indication when responded field (or parameter) started and ended.
Thus, answer is simple: make that indication in your procedure responce!
#instead...

Hi,

Here I can see two options:
1. If you have all the possible output values, you can use some IFs to validate;
2. Change the procedure to not use "NULL" values, but NULL strings...