Dbms_session.set_sql_trace(true) in PL/SQL Code to trace execution

Hi,
I'm working on some legacy PL/SQL Code with the objective of tuning. I added the following to the PL/SQL Body so that I can trace the execution and identify low-hanging-fruit that can be tuned.
I added the following after the BEGIN section of the PL/SQL body:
trace_process_flow_info_sp( this procedure captures the parameters passed into the procedure of the package body);
execute immediate 'alter session set events '||''''||'10046 trace name context forever, level 12'||'''';
dbms_session.set_sql_trace(true);
My objective is to capture the execution of the code, capture the bind variable values, however I am not seeing the bind values in either tkprof or the Trace Analyzer.
Any Ideas on how to see the Bind Variable Values?
Thanks

Level 0 means no binds.Are you sure that this level is available?
According to note 115675.1 there are only four
possible levels (1,4,8,12)Hmmm it seems you are right.
SQL> conn xxx/xxx@xxx
Connected.
SQL> ed
Wrote file afiedt.buf
1* alter session set events '10046 trace name context forever, level 0'
SQL> /
ERROR:
ORA-02194: event specification syntax error 231 (minor error 283) near '0'
SQL> ed
Wrote file afiedt.buf
1* alter session set events '10046 trace name context forever, level 1'
SQL> /
Session altered.
SQL> The same results for 9.2.0.7.0 and 10.2.0.1.0
So OK a correction dbms_session.set_sql_trace(true) means level 1, but anyway it means no binds.
Thank you for your correction, should go and update my article!
Gints Plivna
http://www.gplivna.eu

Similar Messages

Dbms_session.set_sql_trace(true);

Hi experts,
Will you please tell me when a devloper writes
dbms_session.set_sql_trace(true);
In his pl/sql code.What is his exact intention behind it.
Regards
Rajat

http://www.oracle.com/pls/db111/search?remark=quick_search&word=sql+trace&partno=

How to run an external application from PL/SQL code?

Hi,
I want to call an application like "Notepad" from PL/SQL code in a Windows2000 server. Is there any way to do that?
Thanks, best regards.
Paulo.

declare
r varchar(4000);
begin
dbms_java.set_output(10000);
system_util.runshell('sh /ora9/runBackup.sh', r);
dbms_output.put_line(r);
end;
System_util package is
CREATE OR REPLACE PACKAGE System_Util IS
*System: Generic
*Package Name: System_util
*Description: This is an open source package which holds regular used
     * methods by developers and dba's.
*Created by:        Rae Smith
*Created Date:       27/06/2001
*Notes: This ia an free open source package that holds no warranty and
* therefore no-one connected to the development of this package
* can be made reasponsible for any outcomes by it's use.
MODIFICATION LOG**************************************************************
*DETAILS                                    DATE          VERS          CHANGED BY
*===============================================================================
*Created                                 27-06-2001     1.0           Rae Smith
     /********************************* Public Methhods ***************************************/
     --- getDir returns the first directory value held in the init.ora file
     FUNCTION getDir RETURN VARCHAR2;
     --- getPrev.. returns the prevoise day from a gievn date
     FUNCTION getPrevSat(pDate IN DATE) RETURN DATE;
     FUNCTION getPrevSun(pDate IN DATE) RETURN DATE;
     FUNCTION getPrevMon(pDate IN DATE) RETURN DATE;
     FUNCTION getPrevTue(pDate IN DATE) RETURN DATE;
     FUNCTION getPrevWed(pDate IN DATE) RETURN DATE;
     FUNCTION getPrevThu(pDate IN DATE) RETURN DATE;
     FUNCTION getPrevFri(pDate IN DATE) RETURN DATE;
     --- isNumber returns TRUE or FALSE depending on a datatype passed
     FUNCTION isNumber(pnumber IN VARCHAR2) RETURN BOOLEAN;
     FUNCTION isNumber(pnumber IN NUMBER) RETURN BOOLEAN;
     FUNCTION isNumber(pnumber IN DATE) RETURN BOOLEAN;
     --- The writeFile allow you to write data to a file
     --- writeFile has 2 Versions
     --- v1 pass in the file name and the text to write to a file.
     --- v2 pass in the file name, dbms_sql.varhar2s object
     --- and the amount of rows to procces at a time
     --- This enables you to write to afile in batch mode
     PROCEDURE writeFile(pName IN VARCHAR2, pText IN VARCHAR2);
     PROCEDURE writeFile(pName IN VARCHAR2, pText IN DBMS_SQL.VARCHAR2S, pRows IN PLS_INTEGER);
     --- The appendFile methods allow you to append data to a file
--- This also has the inteligents to create the file if ts does not exist.
     --- appendFile has 2 Versions
     --- v1 pass in the file name and the text to write to a file.
     --- v2 pass in the file name, dbms_sql.varhar2s object
     --- and the amount of rows to procces at a time
     --- This enables you to write to afile in batch mode
     PROCEDURE appendFile(pName IN VARCHAR2, pText IN DBMS_SQL.VARCHAR2S, pRows IN PLS_INTEGER);
     PROCEDURE appendFile(pName IN VARCHAR2, pText IN VARCHAR2);
     --- The clearFile clears the data from a file.
     PROCEDURE clearFile(pName IN VARCHAR2);
     --- checkSyntax is a quick syntax checker for sql statements the is a limit to
     --- the size used in the statement. If you have a error with
     --- a statement then pass in the statement watch as it displays
     --- the point where the error arose.
     PROCEDURE checkSyntax(pSql IN VARCHAR2);
     --- isEmpty this returns TRUE or FALSE
     FUNCTION isEmpty(pValue IN VARCHAR2) RETURN BOOLEAN;
     --- getTimeInMins returns the time in minutes for a specified date
     FUNCTION getTimeInMins (pDate IN DATE) RETURN NUMBER;
     --PROCEDURE get_time_in_mins (pDate IN DATE);
     --- incDate returns a specified date incremented by value
     FUNCTION incDate(pInc IN NUMBER DEFAULT .999999, pDate IN DATE DEFAULT SYSDATE) RETURN DATE;
     --- decDate returns a specified date decremented by value
     FUNCTION decDate(pInc IN NUMBER DEFAULT .999999, pDate IN DATE DEFAULT SYSDATE) RETURN DATE;
     --- getTime returns the time in milliseconds
     FUNCTION getTime RETURN NUMBER;
     --- daysDiff returns the amount of days between two values
     FUNCTION daysDiff(pHigh IN DATE, pLow IN DATE) RETURN NUMBER;
     --- difference returns the diffeence between two numbers always
     --- taking the lowest away from the highest
     FUNCTION difference(pAnum IN NUMBER,pBnum IN NUMBER)RETURN NUMBER;
     --- total returns the value of two numbers added together
     FUNCTION total(pAnum IN NUMBER, pBnum IN NUMBER)RETURN NUMBER;
     --- numberToWords returns the string for a number passed in
     FUNCTION numberToWords(pNumb IN NUMBER) RETURN VARCHAR2;
     --- runShell allows you to run operating commands from pl/sql
     --- Only available with 8i
     --- PROCEDURE runShell(pCmnd IN VARCHAR2, pErrMsg IN OUT VARCHAR2);
     /**************************** Public Vaiables *******************************/
     --- Public variable that holds the operating system directory
     --- that the can be written to from withing the database.
     vDir VARCHAR2(50);
END;
CREATE OR REPLACE PACKAGE BODY System_Util IS
     FUNCTION getDir RETURN VARCHAR2
     IS
     BEGIN
          RETURN vDir;
     EXCEPTION
          WHEN OTHERS THEN
               dbms_output.put_line('ERROR...ERROR...System_Util.getDir');
               RAISE;
     END getDir;
     /**** Private module to get the first directory for utl_file to use ****/
     PROCEDURE getDir
     IS
          CURSOR cDir(p1 IN VARCHAR2)
          IS
          SELECT DECODE(INSTR(value, ','), 0, value, SUBSTR(value, 1, INSTR(value, ',')-1)) dir
          FROM v$parameter
          WHERE name = p1;
     BEGIN
          FOR rDir IN cDir('utl_file_dir') LOOP
               vDir := rDir.dir;
          END LOOP;
     EXCEPTION
          WHEN OTHERS THEN
               dbms_output.put_line('ERROR...ERROR...System_Util.getDir');
               RAISE;
     END getDir;
     FUNCTION getPrevDate(pDate IN DATE, pDay IN VARCHAR2) RETURN DATE
     IS
     BEGIN
          RETURN NEXT_DAY(pDate - 7, pDay);
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevDate;
     FUNCTION getPrevSat(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'saturday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevSat;
     FUNCTION getPrevSun(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'sunday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevSun;
     FUNCTION getPrevMon(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'monday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevMon;
     FUNCTION getPrevTue(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'tuesday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevTue;
     FUNCTION getPrevWed(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'wednesday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevWed;
     FUNCTION getPrevThu(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'thursday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevThu;
     FUNCTION getPrevFri(pDate IN DATE) RETURN DATE
     IS
     BEGIN
          RETURN getPrevDate(pDate, 'friday');
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getPrevFri;
     FUNCTION isNumber(pNumber IN VARCHAR2) RETURN BOOLEAN
     IS
     BEGIN
          IF TO_NUMBER(pNumber)> 0 THEN
               RETURN TRUE;
          ELSE
               RETURN FALSE;
          END IF;
     EXCEPTION
          WHEN OTHERS THEN
               RETURN FALSE;
     END isNumber;
     FUNCTION isNumber(pNumber IN NUMBER) RETURN BOOLEAN
     IS
     BEGIN
          IF TO_NUMBER(pNumber) > 0 THEN
               RETURN TRUE;
          ELSE
               RETURN FALSE;
          END IF;
     EXCEPTION
          WHEN OTHERS THEN
          RETURN FALSE;
     END isNumber;
     FUNCTION isNumber(pNumber IN DATE) RETURN BOOLEAN
     IS
     BEGIN
          IF TO_NUMBER(TO_CHAR(pNumber, 'YYYYMMDD')) > 0 THEN
               RETURN TRUE;
          ELSE
               RETURN FALSE;
          END IF;
     EXCEPTION
          WHEN OTHERS THEN
               RETURN FALSE;
     END isNumber;
     PROCEDURE writeFile(pName IN VARCHAR2, pText IN VARCHAR2)
     IS
          vFtype utl_file.file_type;
     BEGIN
          vFtype := UTL_FILE.FOPEN(vDir, pName,'w');
          UTL_FILE.PUT_LINE(vFtype,pText);
          UTL_FILE.FCLOSE(vFtype);
     EXCEPTION
          WHEN OTHERS THEN
               UTL_FILE.FCLOSE(vFtype);
               RAISE;
     END writeFile;
     PROCEDURE writeFile(pName IN VARCHAR2, pText IN VARCHAR2, pFtyp IN OUT utl_file.file_type)
     IS
          vFtype utl_file.file_type;
     BEGIN
          vFtype := UTL_FILE.FOPEN(vDir, pName,'w');
          UTL_FILE.PUT_LINE(vFtype,pText);
          UTL_FILE.FCLOSE(vFtype);
     EXCEPTION
          WHEN OTHERS THEN
               UTL_FILE.FCLOSE(vFtype);
               RAISE;
     END writeFile;
     PROCEDURE writeFile(pName IN VARCHAR2, pText IN DBMS_SQL.VARCHAR2S, pRows IN PLS_INTEGER)
     IS
          vFtype utl_file.file_type;
          vText VARCHAR2(2000);
          vCnt BINARY_INTEGER;
          vRem BINARY_INTEGER;
          vRowcnt PLS_INTEGER := 0;
     BEGIN
          vRem := MOD(pText.COUNT, pRows);
          vFtype := UTL_FILE.FOPEN(vDir, pName, 'w');
          vCnt := pText.FIRST;
          LOOP
               EXIT WHEN vCnt IS NULL;
          vRowcnt := vRowcnt + 1;
               IF vCnt = pText.LAST THEN
                    vText := vText||pText(vCnt);
                    UTL_FILE.PUTF(vFtype,vText);
                    UTL_FILE.FFLUSH(vFtype);
                    vText := '';
               ELSIF MOD(vCnt, pRows) = 0 THEN
                    vText := vText||pText(vCnt)||'\n';
                    UTL_FILE.PUTF(vFtype,vText);
                    UTL_FILE.FFLUSH(vFtype);
                    vText := '';
               ELSIF vRowcnt = vRem THEN
                    vText := vText||pText(vCnt)||'\n';
                    UTL_FILE.PUTF(vFtype,vText);
                    UTL_FILE.FFLUSH(vFtype);
               ELSE
                    vText := vText||pText(vCnt)||'\n';
               END IF;
               vCnt := pText.NEXT(vCnt);
          END LOOP;
          UTL_FILE.FCLOSE(vFtype);
     EXCEPTION
          WHEN OTHERS THEN
               dbms_output.put_line('ERROR...ERROR...SYSTEM_UTIL.WRITE_FILE');
               UTL_FILE.FCLOSE(vFtype);
               RAISE;
     END writeFile;
     PROCEDURE appendFile(pName IN VARCHAR2, pText IN DBMS_SQL.VARCHAR2S, pRows IN PLS_INTEGER)
     IS
          vFtype utl_file.file_type;
          vText VARCHAR2(2000);
          vCnt BINARY_INTEGER;
          vRem BINARY_INTEGER;
          vMode VARCHAR2(2) := 'a';
          vRowcnt PLS_INTEGER := 0;
     BEGIN
          vRem := MOD(pText.COUNT, pRows);
          vFtype := UTL_FILE.FOPEN(vDir, pName, vMode);
          vCnt := pText.FIRST;
          LOOP
               EXIT WHEN vCnt IS NULL;
               vRowcnt := vRowcnt + 1;
               IF vCnt = pText.LAST THEN
                    vText := vText||pText(vCnt);
                    UTL_FILE.PUTF(vFtype,vText);
                    UTL_FILE.FFLUSH(vFtype);
                    vText := '';
               ELSIF MOD(vCnt, pRows) = 0 THEN
                    vText := vText||pText(vCnt)||'\n';
                    UTL_FILE.PUTF(vFtype,vText);
                    UTL_FILE.FFLUSH(vFtype);
                    vText := '';
               ELSIF vRowcnt = vRem THEN
                    vText := vText||pText(vCnt)||'\n';
                    UTL_FILE.PUTF(vFtype,vText);
                    UTL_FILE.FFLUSH(vFtype);
               ELSE
                    vText := vText||pText(vCnt)||'\n';
               END IF;
               vCnt := pText.NEXT(vCnt);
          END LOOP;
               UTL_FILE.FCLOSE(vFtype);
     EXCEPTION
          WHEN UTL_FILE.INVALID_OPERATION THEN
               IF vMode = 'a' THEN
                    writeFile(pName, pText, pRows);
               ELSE
                    RAISE;
          END IF;
     WHEN OTHERS THEN
          dbms_output.put_line('ERROR...ERROR...SYSTEM_UTIL.APPENDFILE');
          UTL_FILE.FCLOSE(vFtype);
          RAISE;
     END appendFile;
     PROCEDURE appendFile(pName IN VARCHAR2, pText IN VARCHAR2)
     IS
          vFtype utl_file.file_type;
          vMode VARCHAR2(2) := 'a';
     BEGIN
          vFtype := UTL_FILE.FOPEN(vDir, pName, vMode);
          UTL_FILE.PUTF(vFtype, pText);
          UTL_FILE.FFLUSH(vFtype);
          UTL_FILE.FCLOSE(vFtype);
     EXCEPTION
     WHEN UTL_FILE.INVALID_OPERATION THEN
     IF vMode = 'a' THEN
          writeFile(pName, pText);
     ELSE
          RAISE;
     END IF;
     WHEN OTHERS THEN
          dbms_output.put_line('ERROR...ERROR...SYSTEM_UTIL.APPENDFILE');
          UTL_FILE.FCLOSE(vftype);
          RAISE;
     END appendFile;
     PROCEDURE clearFile(pName IN VARCHAR2)
     IS
          vFtype utl_file.file_type;
          vText VARCHAR2(2000);
          vCnt BINARY_INTEGER;
          vRem BINARY_INTEGER;
          vRowcnt PLS_INTEGER := 0;
     BEGIN
          vFtype := UTL_FILE.FOPEN(vDir, pName, 'w');
          UTL_FILE.PUTF(vFtype,'');
          UTL_FILE.FFLUSH(vFtype);
          UTL_FILE.FCLOSE(vFtype);
     EXCEPTION
     WHEN OTHERS THEN
     dbms_output.put_line('ERROR...ERROR...System_Util.CLEARFILE');
     UTL_FILE.FCLOSE(vFtype);
     RAISE;
     END clearFile;
     PROCEDURE checkSyntax(pSql IN VARCHAR2)
     IS
     sqlCur PLS_INTEGER := DBMS_SQL.OPEN_CURSOR;
     errPos PLS_INTEGER;
     sqlStmt VARCHAR2(2000);
     BEGIN
          sqlStmt := pSql;
          DBMS_SQL.PARSE(sqlCur, sqlStmt, DBMS_SQL.NATIVE);
     EXCEPTION
          WHEN OTHERS THEN
               errPos := DBMS_SQL.LAST_ERROR_POSITION;
               DBMS_OUTPUT.PUT_LINE(SQLERRM);
               DBMS_OUTPUT.PUT_LINE(sqlStmt);
               DBMS_OUTPUT.PUT_LINE(' ');
               DBMS_OUTPUT.PUT_LINE(LPAD('^', errPos, '-'));
               DBMS_SQL.CLOSE_CURSOR(sqlCur);
     END checkSyntax;
     FUNCTION isEmpty(pValue IN VARCHAR2) RETURN BOOLEAN
     IS
     BEGIN
          IF pValue IS NULL OR pValue = '' OR pValue = ' ' THEN
               RETURN TRUE;
          ELSE
               RETURN FALSE;
          END IF;
     END isEmpty;
     FUNCTION getTimeInMins (pDate IN DATE) RETURN NUMBER
     IS
          vHours NUMBER;
          vMins NUMBER;
          vRetval PLS_INTEGER;
     BEGIN
          vHours := TO_NUMBER(TO_CHAR(pDate,'HH24'));
          vMins := TO_NUMBER(TO_CHAR(pDate,'MI'));
          vRetval := ((60 * vHours) + vMins);
          RETURN vRetval;
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getTimeInMins;
     PROCEDURE getTimeInMins (pDate IN DATE)
     IS
          vHours NUMBER;
          vMins NUMBER;
          vRetval PLS_INTEGER;
     BEGIN
          vHours := TO_NUMBER(TO_CHAR(pDate,'HH24'));
          vMins := TO_NUMBER(TO_CHAR(pDate,'MI'));
          vRetval := ((60 * vHours) + vMins);
          DBMS_OUTPUT.PUT_LINE('The time IN minutes IS: '||vRetval);
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END getTimeInMins;
     FUNCTION incDate(pInc IN NUMBER DEFAULT .999999, pDate IN DATE DEFAULT SYSDATE) RETURN DATE
     IS
     BEGIN
     RETURN (TO_DATE(TO_CHAR(pDate + pInc, 'DD/MM/YYYY HH24:MI:SS'), 'DD/MM/YYYY HH24:MI:SS'));
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END incDate;
     FUNCTION decDate(pInc IN NUMBER DEFAULT .999999, pDate IN DATE DEFAULT SYSDATE) RETURN DATE
     IS
     BEGIN
     RETURN (TO_DATE(TO_CHAR(pDate - pInc, 'DD/MM/YYYY HH24:MI:SS'), 'DD/MM/YYYY HH24:MI:SS'));
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END decDate;
     FUNCTION getTime RETURN NUMBER
     IS
     BEGIN
          RETURN dbms_utility.get_time;
     END getTime;
     FUNCTION daysDiff(pHigh IN DATE, pLow IN DATE) RETURN NUMBER
     IS
          vHighdate DATE;
          vLowdate DATE;
     BEGIN
     IF pHigh > pLow THEN
               vHighdate := TO_DATE(TO_CHAR(pHigh, 'YYYYMMDD'), 'YYYYMMDD');
               vLowdate := TO_DATE(TO_CHAR(pLow, 'YYYYMMDD'), 'YYYYMMDD');
     ELSIF pLow > pHigh THEN
               vHighdate := TO_DATE(TO_CHAR(pLow, 'YYYYMMDD'), 'YYYYMMDD');
               vLowdate := TO_DATE(TO_CHAR(pHigh, 'YYYYMMDD'), 'YYYYMMDD');
     END IF;
          RETURN (vHighdate - vLowdate);
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END daysDiff;
     PROCEDURE dateCheck(pDateFrom IN OUT DATE, pDateTo IN OUT DATE)
     IS
          /* Declare the variable to hold the "from" date */
          vDateFrom DATE;
     BEGIN
          /* If either date_from or date_to is null then set to todays date **
          ** using the sysdate **
          ** today's DATE AND IN the correct format */
          pDateFrom := NVL(pDateFrom, SYSDATE);
          pDateTo := NVL(pDateTo, SYSDATE);
          /* Check that the from date is not greater than the to date if so **
          ** use the system_util.incDate to Increment the date by 1 day */
          IF (pDateFrom > pDateTo) THEN
          vDateFrom := pDateFrom;
          pDateTo := System_Util.incDate(1, vDateFrom);
          END IF;
     EXCEPTION
          WHEN OTHERS THEN
          RAISE;
     END;
     /* calculates the difference of two numbers always taken the high from the low*/
     FUNCTION difference(pAnum IN NUMBER, pBnum IN NUMBER)RETURN NUMBER
     IS
          vTotal NUMBER;
     BEGIN
          IF (pAnum > pBnum )OR (pAnum = pBnum)THEN
               vTotal := (pAnum - pBnum);
          ELSIF (pAnum < pBnum) THEN
               vTotal := (pBnum - pAnum);
          END IF;
          RETURN (vTotal);
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END difference;
     /* calculates the Total of two numbers*/
     FUNCTION total(pAnum IN NUMBER, pBnum IN NUMBER)RETURN NUMBER
     IS
          vTotal NUMBER;
     BEGIN
          vTotal := (pAnum + pBnum);
     RETURN (vTotal);
     EXCEPTION
          WHEN OTHERS THEN
               RAISE;
     END total;
     FUNCTION numberToWords(pNumb IN NUMBER) RETURN VARCHAR2
     IS
          vRetval VARCHAR2(255);
          vNumb PLS_INTEGER;
     BEGIN
          vNumb := pNumb;
          vRetval := REPLACE(TO_CHAR(TO_DATE(vNumb,'j'),'jsp'),'-',' ');
          RETURN (vRetval);
     EXCEPTION
          WHEN OTHERS THEN
          RAISE;
     END;
/*************** Only Available on 8i ********************************\
     FUNCTION Catcherr(pStr IN VARCHAR2) RETURN VARCHAR2
     IS
          LANGUAGE JAVA
          NAME 'catchErr.run(java.lang.String) return String';
     PROCEDURE runShell(pCmnd IN VARCHAR2, pErrMsg IN OUT VARCHAR2)
     IS
     BEGIN
          pErrMsg := Catcherr(pCmnd);
     EXCEPTION
     WHEN OTHERS THEN
          RAISE;
     END runShell;
BEGIN
getDir;
END;

What does where 1=1 mean in sql code

I am going throough someones sql code and they have used where 1=1 in alot of places what is this for... it doesnt make sense to me...

"create table emp1 as select * from emp where 1=1"
While your statement that this will create a copy of the emp table is true, the predicate is meaningless.
CREATE TABLE emp1 AS
SELECT * FROM empwill do the exact same thing with less typing.
Puppethead
The same argument applies to your use of the predicate in development. WHERE 1 = 1 does not change the meaning of the query, no matter how many other predicates you add or remove from the query. The result of the query will be governed by the meaningful predicates in the WHERE clause.
WHERE 1 = 1 is noise, and is ignored by the optimizer.
SQL> EXPLAIN PLAN SET statement_id = 'john' for
2 SELECT COUNT(*) FROM demographic
3 WHERE patient_first_name = 'JOHN';
Explained.
SQL> SELECT plan_table_output
2 FROM TABLE(dbms_xplan.display('plan_table','john','serial'));
PLAN_TABLE_OUTPUT
| Id | Operation            | Name        | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT     |              |     1 |    17 | 1969 |
|   1 | SORT AGGREGATE      |              |     1 |    17 |       |
|* 2 |   TABLE ACCESS FULL | DEMOGRAPHIC | 1547 | 26299 | 1969 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   2 - filter("DEMOGRAPHIC"."PATIENT_FIRST_NAME"='JOHN')
Note: cpu costing is offNote that explain plan reports that it used the predicate as a filter during the full scan. Now, 1 = 1:
SQL> EXPLAIN PLAN SET statement_id = 'johna' for
2 SELECT COUNT(*) FROM demographic
3 WHERE 1 = 1;
Explained.
SQL> SELECT plan_table_output
2 FROM TABLE(dbms_xplan.display('plan_table','johna','serial'));
PLAN_TABLE_OUTPUT
| Id | Operation             | Name          | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT      |                |     1 |       |   119 |
|   1 | SORT AGGREGATE       |                |     1 |       |       |
|   2 |   INDEX FAST FULL SCAN| DEMOGRAPHIC_4 |   154K|       |   119 |
Note: cpu costing is offNote that there is no predicate used. Even combining both, I still get only one predicate evaluated:
SQL> EXPLAIN PLAN SET statement_id = 'johnb' for
2 SELECT COUNT(*) FROM demographic
3 WHERE patient_first_name = 'JOHN' and
4        1 = 1;
Explained.
SQL> SELECT plan_table_output
2 FROM TABLE(dbms_xplan.display('plan_table','johnb','serial'));
PLAN_TABLE_OUTPUT
| Id | Operation            | Name        | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT     |              |     1 |    17 | 1969 |
|   1 | SORT AGGREGATE      |              |     1 |    17 |       |
|* 2 |   TABLE ACCESS FULL | DEMOGRAPHIC | 1547 | 26299 | 1969 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   2 - filter("DEMOGRAPHIC"."PATIENT_FIRST_NAME"='JOHN')
Note: cpu costing is offJohn

Got the following reply from db-kernel: SQL-Code :-903

Dear Experts,
I am having a problem running MaxDB Data backup on Netbackup.... Please se log below and suggest.
2011-04-11 13:30:38
Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2011-04-11 13:30:39
Checking existence and configuration of Backint for MaxDB.
    Using configuration variable 'BSI_ENV' = 'C:\Netbackup_Script\bsi_backint_daily.env' as path of the configuration file of Backint for MaxDB.
    Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value 'C:\Netbackup_Script\bsi_backint_daily.env'.
    Reading the Backint for MaxDB configuration file 'C:\Netbackup_Script\bsi_backint_daily.env'.
        Found keyword 'BACKINT' with value 'D:\sapdb\KGP\db\bin\backint.exe'.
        Found keyword 'INPUT' with value 'E:\sapdb\data\wrk\KGP\backint.input'.
        Found keyword 'OUTPUT' with value 'E:\sapdb\data\wrk\KGP\backint.output'.
        Found keyword 'ERROROUTPUT' with value 'E:\sapdb\data\wrk\KGP\backint.error'.
        Found keyword 'PARAMETERFILE' with value 'C:\Netbackup_Script\backint_parameter_daily.txt'.
    Finished reading of the Backint for MaxDB configuration file.
    Using 'D:\sapdb\KGP\db\bin\backint.exe' as Backint for MaxDB program.
    Using 'E:\sapdb\data\wrk\KGP\backint.input' as input file for Backint for MaxDB.
    Using 'E:\sapdb\data\wrk\KGP\backint.output' as output file for Backint for MaxDB.
    Using 'E:\sapdb\data\wrk\KGP\backint.error' as error output file for Backint for MaxDB.
    Using 'C:\Netbackup_Script\backint_parameter_daily.txt' as parameter file for Backint for MaxDB.
    Using '300' seconds as timeout for Backint for MaxDB in the case of success.
    Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
    Using 'E:\sapdb\data\wrk\KGP\dbm.knl' as backup history of a database to migrate.
    Using 'E:\sapdb\data\wrk\KGP\dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
Check passed successful.
2011-04-11 13:30:39
Checking medium.
Check passed successfully.
2011-04-11 13:30:39
Preparing backup.
    The environment variable 'BSI_ENV' has already the value 'C:\Netbackup_Script\bsi_backint_daily.env'.
    Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
    Setting environment variable 'BI_REQUEST' to value 'NEW'.
    Setting environment variable 'BI_BACKUP' to value 'FULL'.
    Constructed Backint for MaxDB call 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -p C:\Netbackup_Script\backint_parameter_daily.txt -i E:\sapdb\data\wrk\KGP\backint.input -c'.
    Created temporary file 'E:\sapdb\data\wrk\KGP\backint.output' as output for Backint for MaxDB.
    Created temporary file 'E:\sapdb\data\wrk\KGP\backint.error' as error output for Backint for MaxDB.
    Writing 'D:\sapdb\pipe2 #PIPE' to the input file.
Prepare passed successfully.
2011-04-11 13:30:39
Starting database action for the backup.
    Requesting 'SAVE DATA QUICK TO 'D:\sapdb\pipe2' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKDBFULL'' from db-kernel.The database is working on the request.
2011-04-11 13:30:39
Waiting until database has prepared the backup.
    Asking for state of database.
    2011-04-11 13:30:39 Database is still preparing the backup.
    Waiting 1 second ... Done.
    Asking for state of database.
    2011-04-11 13:30:41 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2011-04-11 13:30:41
Starting Backint for MaxDB.
    Starting Backint for MaxDB process 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -p C:\Netbackup_Script\backint_parameter_daily.txt -i E:\sapdb\data\wrk\KGP\backint.input -c >>E:\sapdb\data\wrk\KGP\backint.output 2>>E:\sapdb\data\wrk\KGP\backint.error'.
    Process was started successfully.
Backint for MaxDB has been started successfully.
2011-04-11 13:30:41
Waiting for end of the backup operation.
    2011-04-11 13:30:41 The backup tool is running.
    2011-04-11 13:30:41 The database is working on the request.
    2011-04-11 13:30:43 The database has finished work on the request.
    Receiving a reply from the database kernel.
    Got the following reply from db-kernel:
        SQL-Code              :-903
    2011-04-11 13:30:43 The backup tool is running.
    2011-04-11 13:30:44 The backup tool process has finished work with return code 2.
The backup operation has ended.
2011-04-11 13:30:44
Filling reply buffer.
    Have encountered error -24920:
        The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
    Constructed the following reply:
        ERR
        -24920,ERR_BACKUPOP: backup operation was unsuccessful
        The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
Reply buffer filled.
2011-04-11 13:30:44
Cleaning up.
    Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.output)----
        Reading parameter file C:\Netbackup_Script\backint_parameter_daily.txt.
        Using D:\sapdb\KGP\db\bin\backint.exe as Backint for Oracle.
        Using C:\Netbackup_Script\nt_initKGPdaily.utl as parameterfile of Backint for Oracle.
        Using E:\sapdb\data\wrk\KGP\backinthistory.log as history file.
        Using E:\sapdb\data\wrk\KGP\backintoracle.in as input of Backint for Oracle.
        Using E:\sapdb\data\wrk\KGP\backintoracle.out as output of Backint for Oracle.
        Using E:\sapdb\data\wrk\KGP\backintoracle.err as error output of Backint for Oracle.
        Using staging area D:\sapdb\Stage1 with a size of 2147483648 bytes.
        Reading input file E:\sapdb\data\wrk\KGP\backint.input.
        Backing up pipe D:\sapdb\pipe2.
        Found 1 entry in the input file.
        Starting the backup.
        Starting pipe2file program(s).
        Waiting for creation of temporary files.
        1 temporary file is available for backup.
        Calling Backint for Oracle at 2011-04-11 13:30:43.
        Calling 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -p C:\Netbackup_Script\nt_initKGPdaily.utl -i E:\sapdb\data\wrk\KGP\backintoracle.in -c' .
        Backint for Oracle ended at 2011-04-11 13:30:43 with return code 2.
        Backint for Oracle output: Reading parameter file C:\Netbackup_Script\nt_initKGPdaily.utl.
        Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backint4oracle.in as input of Backint for Oracle.
        Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backint4oracle.out as output of Backint for Oracle.
        Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backint4oracle.err as error output of Backint for Oracle.
        Backint for Oracle output: Using staging area D:\sapdb\Stage1 with a size of 2147483648 bytes.
        Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backinthistory.log as history file.
        Backint for Oracle output: Using D:\sapdb\KGP\db\bin\backint.exe as Backint for Oracle.
        Backint for Oracle output:
        Backint for Oracle output: Reading input file E:\sapdb\data\wrk\KGP\backintoracle.in.
        Backint for Oracle output: Backing up file D:\sapdb\Stage1.0.
        Backint for Oracle output: Found 1 entry in the input file.
        Backint for Oracle output:
        Backint for Oracle output: Starting the backup.
        Backint for Oracle output: Starting pipe2file program(s).
        Backint for Oracle output:
        Backint for Oracle output: Calling Backint for Oracle at 2011-04-11 13:30:43.
        Backint for Oracle output: Calling 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -i E:\sapdb\data\wrk\KGP\backint4oracle.in -c' .
        Backint for Oracle output: Backint for Oracle ended at 2011-04-11 13:30:43 with return code 2.
        Backint for Oracle output: Backint for Oracle output: Reading parameter file .
        Backint for Oracle output: Backint for Oracle output:
        Backint for Oracle output: Backint for Oracle output:
        Backint for Oracle output: Backint for Oracle error output: No staging area is defined in the parameter file.
        Backint for Oracle output: Backint for Oracle error output: The path of Backint for Oracle is not defined in the parameter file.
        Backint for Oracle output: Backint for Oracle error output: The name of the history file is not defined in the parameter file.
        Backint for Oracle output: Backint for Oracle error output: The name of the input file of Backint for Oracle is not defined in the parameter file.
        Backint for Oracle output: Backint for Oracle error output: The name of the output file of Backint for Oracle is not defined in the parameter file.
        Backint for Oracle output: Backint for Oracle error output: The name of the error output file of Backint for Oracle is not defined in the parameter file.
        Backint for Oracle output: Backint for Oracle error output:
        Backint for Oracle output:
        Backint for Oracle output: Finished the backup unsuccessfully.
        Backint for Oracle output:
        Backint for Oracle output: #ERROR D:\sapdb\Stage1.0
        Backint for Oracle output:
        Backint for Oracle error output: Backint for Oracle was unsuccessful.
        Backint for Oracle error output:
        Finished the backup unsuccessfully.
        #ERROR D:\sapdb\pipe2
End of output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.output)----
    Removed Backint for MaxDB's temporary output file 'E:\sapdb\data\wrk\KGP\backint.output'.
    Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.error)----
        Backint for Oracle was unsuccessful.
End of error output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.error)----
    Removed Backint for MaxDB's temporary error output file 'E:\sapdb\data\wrk\KGP\backint.error'.
    Removed the Backint for MaxDB input file 'E:\sapdb\data\wrk\KGP\backint.input'.
Have finished clean up successfully.

>     Requesting 'SAVE DATA QUICK TO 'D:\sapdb\pipe2' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKDBFULL'' from db-kernel.The database is working on the request.
This seems to be your problem, the pipe is wrongly defined. On Windows it looks like
\\.\pipe1
see
http://msdn.microsoft.com/en-us/library/aa365783.aspx
Markus

PL/SQL code written in db or in application...????

Hi ,
Which is the best...at performance , maintability... e.t.c.???
To write PL/SQL as validation process of data values going to be inserted in db:
1) as db trigger (before insert or update row-level trigger)
2) in application level - in Forms10g...
This PL/SQL code compares some pairs of data values only.... there DML statement....
Both db server and App server are considered to be or in the same machine or in two machines very close to each other...
Note: i use Db10g .
Thanks...
Sim

It is all about moving parts. How many there are. Where they are located.
The less moving parts, the less the complexity, the bugs - and the better the performance (less wheels to turn to crunch data), the easier the maintenance and the better the flexibility.
Part of this is having the moving parts close to the data. Kind of obvious - what is faster? Shipping data from the db engine to a front-end application via a app server and web server? Or shipping the data from the db (SQL) engine to a PL/SQL process running as part and parcel of db instance? IPC is significantly faster than TCP/IP.
Having the moving parts close to the data also means that it can scale with the data. Oracle is good at scalability. It is designed at its very core to be scalable. Partitions to reduce I/O. Shared Server to reduce o/s resource footprint per client session. Shared pool to re-use SQL. DB buffer to cache data. RAC to run multiple db instances for a single physical database. Etc. Etc.
With the application moving parts being close to the data, it inherits this scalability. You can "multi-thread" application code using table pipelines. You have access to forking application code using background processes (DBMS_JOB and DBMS_SCHEDULER). You have bulk processing in order to transfer more data per SQL engine call, between the buffer cache and your application, and thus also reduce expensive context switching.
This list goes on and on.
All this is summarised into the following rules.
Rule 1. Do it in SQL.
Rule 2. Only when SQL cannot do it, use PL/SQL. (e.g. SQL is not suited for managing and controlling process flow - PL/SQL is)
Rule 3. Only when PL/SQL cannot do it, use <insert-language-here> (e.g. PL/SQL cannot render a Windows grid on the client - but Delphi/C#//Java can).
Also keep in mind that in the modern client-server paradigm we deal with a web architecture. Which means the client is a web browser. And this means that PL/SQL can pass the data (HTML) required by the client (web browser) to render the User Interface.
Have a look at APEX (Oracle's Application Express) for how this works. http://apex.oracle.com
All you need to develop web applications is APEX (a PL/SQL product suite in the database) and a web browser. Kickass stuff... :-)

REPORT WITH PL/SQL CODE

DECLARE
SQ VARCHAR2(100);
BEGIN
SQ := 'SELECT * FROM EMP WHERE EMPNO=7788';
RETURN SQ;
END
THE ABOVE PL/SQL CODE WORKING FINE
BUT I NEED CONDITION BASED ON ENAME
SQ:='SELECT * FROM EMP WHERE ENAME=''SCOTT'';
IT IS GIVEING ERROR
WHAT TO DO?

Hi,
You're missing the final quote - you have the quotes for SCOTT but not the one to close the SQ string:
DECLARE
SQ VARCHAR2(100);
BEGIN
SQ := 'SELECT * FROM EMP WHERE EMPNO=''SCOTT''';
RETURN SQ;
ENDAndy

How to 100% Protect PL/SQL Code By Wrapped in Oracle Database 10g R2

Hello,
Is Possible to 100% Protect PL/SQL Code By Wrapped in Oracle 10g R2 ?
If it is not possible by wrap in oracle 10g R2,
Please, let me suggest, how i will be able to 100% protect PL/SQL code in Oracle Database 10g R2.
Because, I have lot of functions, procedures & package's in my project.
Which is running in field filed.
So, i have needed to protect 100%.
Also, will i convert to al functions, procedures & package's to .pll file ?
And .pll file to .plx file?
Is it possible to convert .plx file to .pll file ?
Please, let know any better solutions in this case....
Regards
Mehedi

Hello,
No, wrapping is not a 100% secure method. It could prevent your code from amateurs, but not from professional hackers. Look at the article http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/wrap.htm#BEHGBJAA
It says: "•Wrapping is not a secure method for hiding passwords or table names.
Wrapping a PL/SQL unit prevents most users from examining the source code, but might not stop all of them."
Edited by: apiminov on 03.12.2012 3:23
Edited by: apiminov on 03.12.2012 3:24

How to reference LEVEL in a TREE's SQL code

Is it possible to somehow reference LEVEL in a tree's sql code so that you can use a decode statement to selectively create links on specific levels only i.e. NOT on the root level?
e.g.
select "CHILD_ID" id,
"PARENT_ID" pid,
"NAME" name,
decode( LEVEL, 1, null,'f?p=' || :APP_ID || ':43:' || :APP_SESSION || '::::P43_CHILD_ID:' || CHILD_ID) link,
null a1,
null a2
from TREETABLE
order by name
one solution I've implemented is to create a DB function e.g.
create or replace function get_tree_level(v_child_id number) return number
is
v_level number(2);
begin
select level
into v_level
from TREETABLE
where child_id=v_child_id
start with child_id=1
connect by prior child_id= parent_id;
return v_level;
end;
and then use
decode( get_tree_level(child_id) 1, null,'f?p=' || :APP_ID || ':43:' || :APP_SESSION || '::::P43_CHILD_ID:' || CHILD_ID) link,
but this is too slow as I have quite a few records in the tree and takes too long to render
regards
Paul P

OK I found a workaround after reading
How to add URL to tree
The view my tree is build on is constructed out of 3 unions and 4 "selects" ( the first select creates the ROOT NODE where "1" is also used as a hard coded foreign key (Parent_id), in the company table.)
I just added a new column called tree_level to the query which is hard coded wrt its level on the hierarchy.
e.g.
CREATE OR REPLACE FORCE VIEW COMCONSTUTREE ("CHILD_ID", "PARENT_ID", "NAME","TREE_LEVEL") AS
select 1 as child_id,to_number(null) as parent_id ,'Company' as name,*1 as tree_level* from dual
UNION
select COM_ID, 1, COM_NAME,2
from company
UNION
select CON_ID,CON_COMPANY_ID, substr(con_name,instr(con_name,' ')+1) ||', '||substr(con_name,1,instr(con_name,' ')-1),3
from contact
UNION
select STU_ID,STU_CONTACT_ID, STU_LAST_NAME||', '||STU_FIRST_NAME ,4
from student;
the tree code now becomes
select "CHILD_ID" id,
"PARENT_ID" pid,
"NAME" name,
decode( tree_level,1, null,'f?p=' || :APP_ID || ':43:' || :APP_SESSION || ':TREE:::P43_CHILD_ID:' ||CHILD_ID) link,
null a1,
null a2
from COMCONSTUTREE"
order by name

PL/SQL Code not working without debug statements

Hi Guys,
I have a pl/sql code in a procedure, logic iterates through almost 40K records, conditional delete and update.
When I execute this code, I dont see the deletes and updates happening, though procedure executes for 8 minutes and exits wihtout any error, execption.
In same procedure when I write some debug statements like dbms_output, then everything seems to be working fine.
I know this scenario happens in Oracle Forms, wehre we use SYNCHRONIZE.
But this is plain pl/sql procedure.
any thoughts on this?
Av.

COMMIT ?
Aside from that, no idea what your procedure looks like, what it does, what version of Oracle you are using, how you are determining "I dont see the deletes and updates happening". etc...
You'd need to provide a slew of information for anyone to give you any meaningful help.
I can only assure you that DBMS_OUTPUT doesn't do magic :)

Can I have a PL/SQL code for LOV

Hi,
I apologize for this dumb question. I have been so out of touch with dev (almost 8 years). Plus new to pl/sql.
I am creating a status report application. On the dashboard, I currently have some metrics (horizontal charts). I wanted to expose these metrics based on filter.
I had created 2 filters. The first one will identify the type (Week, Month, Qtr or Year) and the 2nd filter would be based on the type. For e.g. if I select Month as type, the 2nd filter should show May-12, April-12 etc. Once I select the 2nd filter, I should use them to show the appropriate metrics. The metric that I currently have would show all the projects that users have worked on during the week/month/qtr or year (depending on the 1st and 2nd filter).
On the dashboard region, I added a condition to check if the value for both 1st and 2nd filter is not null. This allows me to show the dashboard only if the 2 filters have been selected.
For the 2nd filter, I need to write a PL/SQL code to show the LOV.
I am assuming that the pl/sql would return a SQL query. The SQL query will be based on week, month etc. Is that right?
Thanks
balaji
Edited by: user644868 on May 17, 2012 11:29 AM

rbalaji2026 wrote:
For the 2nd filter, I need to write a PL/SQL code to show the LOV. Doesn't appear necessary. With filter 2 cascading from filter 1, why not:
select
        /* Week query */
from
where
and     :p1_filter_1 = 'WEEK'
union all
select
        /* Month query */
from
where
and     :p1_filter_1 = 'MONTH'
union all
select
        /* Quarter query */
from
where
and     :p1_filter_1 = 'QUARTER'
union all
select
        /* Year query */
from
where
and     :p1_filter_1 = 'YEAR'

Multiple SQL queries in additional PL/SQL code in Report

Hello gurus,
I have a form in my portal populated some searching parameters and these parameters inserted into some temporary tables such as name_temp, addr_temp. And then I have a report that run based on these parameters, I have added additional PL/SQL code in the report at the time after the header was displayed. The code is as follows:
declare
checkname varchar2(40);
checkaddr varchar2(100);
begin
select emp.name into checkname from emp
where name = (select name from name_temp);
select personnel.addr into checkaddr from personnel
where addr = (select address from addr_temp);
end;
The problem I have is always the first SQL statement was executed, but not the second one, nor the third one. Does PL/SQL only supports one SQL statement per call? Please help. Is there a better way to handle this case?
Thanks.
Vince

Hello gurus,
I have a form in my portal populated some searching parameters and these parameters inserted into some temporary tables such as name_temp, addr_temp. And then I have a report that run based on these parameters, I have added additional PL/SQL code in the report at the time after the header was displayed. The code is as follows:
declare
checkname varchar2(40);
checkaddr varchar2(100);
begin
select emp.name into checkname from emp
where name = (select name from name_temp);
select personnel.addr into checkaddr from personnel
where addr = (select address from addr_temp);
end;
The problem I have is always the first SQL statement was executed, but not the second one, nor the third one. Does PL/SQL only supports one SQL statement per call? Please help. Is there a better way to handle this case?
Thanks.
Vince

How to change the profile value in the pl/sql code without making change in the database

How to change the profile value in the pl/sql code without making change in the database.

I have program ,where if the profiles 'printer and nunber of copies ' are set at the user level, by default when the report completes the O/p will be sent to the printer mentioned in the set-up. but what user wants is
if these Profiles are set for the user running this program automatic printing should not be done.

How can one read a Excel File and Upload into Table using Pl/SQL Code.

How can one read a Excel File and Upload into Table using Pl/SQL Code.
1. Excel File is on My PC.
2. And I want to write a Stored Procedure or Package to do that.
3. DataBase is on Other Server. Client-Server Environment.
4. I am Using Toad or PlSql developer tool.

If you would like to create a package/procedure in order to solve this problem consider using the UTL_FILE in built package, here are a few steps to get you going:
1. Get your DBA to create directory object in oracle using the following command:
create directory TEST_DIR as ‘directory_path’;
Note: This directory is on the server.
2. Grant read,write on directory directory_object_name to username;
You can find out the directory_object_name value from dba_directories view if you are using the system user account.
3. Logon as the user as mentioned above.
Sample code read plain text file code, you can modify this code to suit your need (i.e. read a csv file)
function getData(p_filename in varchar2,
p_filepath in varchar2
) RETURN VARCHAR2 is
input_file utl_file.file_type;
--declare a buffer to read text data
input_buffer varchar2(4000);
begin
--using the UTL_FILE in built package
input_file := utl_file.fopen(p_filepath, p_filename, 'R');
utl_file.get_line(input_file, input_buffer);
--debug
--dbms_output.put_line(input_buffer);
utl_file.fclose(input_file);
--return data
return input_buffer;
end;
Hope this helps.

Query SQL code gets deleted after export to Excel. "Query must have at least one destination field"

Hi all,
I'm getting really frustrated by this Access error. It happens when I export the result of a query through an Access macro to Excel, the first time it runs well but the next time, there is a chance that the query won't run and the error "Query
must have at least one destination field" will be displayed. After that, I try to check the query SQL code and discover the code has vanished. I'm using simple Select query without joins, only "where", "group by" and "order by"
statements.
Thank you in advance for your help,
Jesus
Edit:
One of these queries are like the following (all of them are of this type):
SELECT Field1, field2, field3, field4, field5, Sum(Field6) AS SumOfField6, Sum(Field7) AS SumOfField7
FROM Table1
WHERE Field6 is not null
GROUP BY Field1, field2, field3, field4, field5
Order By Sum(Field6) desc

Hi Peter,
Thank you for your response, I updated the original question with one of the codes.
Thanks,
Jesus

Dbms_session.set_sql_trace(true) in PL/SQL Code to trace execution

Similar Messages

Maybe you are looking for