Maximum size of dbms_scheduler.create_job job_action parameter

i'm running into a problem with the size limit for the dbms_job.submit what parameter... time to move to the dbms_scheduler.create_job package?
can anyone tell me what the maximum size is for the dbms_scheduler.create_job job_action parameter?
appreciate any information that can be provided.

Herald ten Dam wrote:
But how doy come in trouble with this length, normally a call to a procedure (in a package) and do there the job. Don't program the whole pl/sql (C/Java) in the call. With dbms_scheduler you can make also dependencies between jobs, so it is possible to split the functionality.Yes, I completely agree. The only times that I've put PL/SQL anonymous blocks in scheduler actions is when I want to guarantee the fewest dependencies for jobs (or chain steps) that are really critical, such as when you want to send an email or other notification that a failure has occurred. Otherwise I'd just call a procedure.

Similar Messages

DBMS_SCHEDULER.create_job parameter for repeat_interval

how to specify the DBMS_SCHEDULER.create_job repeat_interval parameter for 15 mintues?

You probably want an interval like this:
FREQ=MONTHLY;BYMONTHDAY=2;BYHOUR=20;BYMINUTE=0;BYSECOND=0;You can use the DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING function to test it, like so:
SQL > DECLARE
2 start_date        TIMESTAMP;
3 return_date_after TIMESTAMP;
4 next_run_date     TIMESTAMP;
5 BEGIN
6 start_date :=
7    to_timestamp_tz('01-JAN-2003 10:00:00','DD-MON-YYYY HH24:MI:SS');
8 return_date_after := start_date;
9 FOR i IN 1..5 LOOP
10    DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING(
11      'FREQ=MONTHLY;BYMONTHDAY=2;BYHOUR=20;BYMINUTE=0;BYSECOND=0;',
12      start_date, return_date_after, next_run_date);
13 DBMS_OUTPUT.PUT_LINE('next_run_date: ' || next_run_date);
14 return_date_after := next_run_date;
15 END LOOP;
16 END;
17 /
next_run_date: 01/02/2003 08:00:00.000000 PM
next_run_date: 02/02/2003 08:00:00.000000 PM
next_run_date: 03/02/2003 08:00:00.000000 PM
next_run_date: 04/02/2003 08:00:00.000000 PM
next_run_date: 05/02/2003 08:00:00.000000 PM

What is the maximum size for open_cursors parameter in 11g database

what is the maximum size we can set for open_cursors parameter in 11g database..

Oracle® Database Reference
11g Release 1 (11.1)
Parameter type     Integer
Default value     50
Modifiable     ALTER SYSTEM
Range of values     0 to 65535
Basic     Yes
For details, go to the following link:
http://www.seasongreetings.org/documentation/oracle/database/11.1/server.111/b28320/initparams153.htm

What is the maximum size of the application to download to iPad via GSM. Is it 20 Mb? Is it possible to change this parameter?

What is the maximum size of application to download to iPad via GSM. Is it 20 Mb? Does exist any possibility to change this parameter? In the towm where I live there is lack of wifi and the only possibiluty to download something from Apple Store is to use GSM/3G.

It has partly to do with the carrier. From what I've summized from reviews & feedback online is since Apple iPhone was the most advanced phone on the market when it was initially released the carriers were concerned about using up bandwidth with the apps & movie downloads so a limit was intially set for 10mb max on 3G connection. Later apple raised the limit, against the carrier's advice, to 20mb max.
The interesting part is the limitation doesn't exist on Android phone when they also have large apps & movies which are available for download & they use the same networks the iPhone uses! So why are the iPhone users still limited to the amount they can download at once while the Android users are not. They pay the same for thier data plans, if not less in some cases, that iPhone users do!

Maximum size of a parameter of web service

Hello,
Suppose we have the folowing WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions .....>
   <wsdl:types>
      <xsd:schema .....>
        <xsd:element name="myMethod" >
           <xsd:complexType>
             <xsd:sequence>
                <xsd:element name="myParameter" type="types:MyParameterType"/>
             </xsd:sequence>
           </xsd:complexType>
        </xsd:element>
        <xsd:element name="myMethodResponse">
        </xsd:element>
     </xsd:schema>
   </wsdl:types>
   <wsdl:message name="MyMethodRequestMessage">
        <wsdl:part name="parameters" element="wsdltypes:myMethod"/>
   </wsdl:message>
   <wsdl:message name="MyMethodResponseMessage">
        <wsdl:part name="parameters" element="wsdltypes:myMethodResponse"/>
   </wsdl:message>
   <wsdl:portType      name="MyPortType">
       <wsdl:operation name="myMethod">
         <wsdl:input name="myMethodRequest" message="tns:MyMethodRequestMessage"/>
         <wsdl:output name="myMethodResponse" message="tns:MyMethodResponseMessage"/>
        </wsdl:operation>
   </wsdl:portType>
<wsdl:definitions>What is the maximum size of "myParameter" U advice me to not to exeed ?

Hi,
Based on one of the documents from SAP,
When you are creating dimensions for your application set you should be aware of the following maximums for any one dimension.
u2022 The maximum number of fields in a table (a dimension = 1 table) is 1024.
u2022 The maximum record size is 8064 bytes (a record = 1 row in a table)
The two maximums above relate to the underlying SQL database in which BPC information and data is stored. They need further explanation as to how they relate to a BPC dimension. In BPC a field equals a property. So you can have up to 1024 properties in a dimension. One other factor that has an impact on the actual number of properties you can have in a dimension is the number of levels you have defined. SQL Server creates a set of properties for each level within the dimension. For example, you have 10 properties and three levels in your dimension, your total number of fields is 30. The second limiting factor is the size of the record. To determine record size you have to figure out the number of bytes (a byte equals a character) in each level. Since levels are repeated you only need to figure out the number of bytes in the first level and then multiply that number by the number of levels. To come up with the total number of bytes for a level you simply add up the field size for each field and multiply it by 2 (1 character = 2 bytes).
Hope this gives you some idea.

How to use NULL as an argument in a dbms_scheduler.create_job script?

Hello All,
We are trying to pass a null argument as a parameter to a PL/SQL program after CURRENT_TIMESTAMP. However, every attempt we try is producing errors. Why we are passing the null is another story. Does anyone know of the correct syntax, if there is any, to accomplish passing the null argument as a parameter to a PL/SQL program?
We'd like to continue running with this same script setup and have the passing of the null working.
This is what we've tried and directly below are the results. Any help so far would be appreciated!
begin
dbms_scheduler.create_job ( job_name => 'LOAD_CRF_TRANSACTION',
job_type => 'PLSQL_BLOCK',
job_action => 'begin
DW_CRF.PKG_LPS_CRF_LOAD_TRANS.sp_load_target(''LOAD_CRF'', ''LOAD_LOAN_TRAN'', CURRENT_TIMESTAMP, );
end;',
start_date => sysdate +1/24/59,
enabled => TRUE,
auto_drop => TRUE,
comments => 'LOAD LOAN TRANSACTION TABLE IN DW_CRF ' );
end;
ORA-06550: line ORA-06550: line 2, column 115:
PLS-00103: Encountered the symbol ")" when expecting one of the following:
( - + case mod new not null others <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall merge time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe
<an alternatively-quoted string literal with character set specification>
<an alternatively-q
, column :
begin
dbms_scheduler.create_job ( job_name => 'LOAD_CRF_TRANSACTION',
job_type => 'PLSQL_BLOCK',
job_action => 'begin
DW_CRF.PKG_LPS_CRF_LOAD_TRANS.sp_load_target(''LOAD_CRF'', ''LOAD_LOAN_TRAN'', CURRENT_TIMESTAMP);
end;',
start_date => sysdate +1/24/59,
enabled => TRUE,
auto_drop => TRUE,
comments => 'LOAD LOAN TRANSACTION TABLE IN DW_CRF ' );
end;
ORA-06550: line ORA-06550: line 2, column 21:
PLS-00306: wrong number or types of arguments in call to 'SP_LOAD_TARGET'
ORA-06550: line 2, column 21:
PL/SQL: Statement ignored
, column :
begin
dbms_scheduler.create_job ( job_name => 'LOAD_CRF_TRANSACTION',
job_type => 'PLSQL_BLOCK',
job_action => 'begin
DW_CRF.PKG_LPS_CRF_LOAD_TRANS.sp_load_target(''LOAD_CRF'', ''LOAD_LOAN_TRAN'', CURRENT_TIMESTAMP, NULL);
end;',
start_date => sysdate +1/24/59,
enabled => TRUE,
auto_drop => TRUE,
comments => 'LOAD LOAN TRANSACTION TABLE IN DW_CRF ' );
end;
ORA-20050: ORA-20050: Error Loading PKG_LPS_CRF_LOAD_TRANS Data
ORA-06512: at "DW_CRF.PKG_LPS_CRF_LOAD_TRANS", line 958
ORA-06512: at line 2
begin
dbms_scheduler.create_job ( job_name => 'LOAD_CRF_TRANSACTION',
job_type => 'PLSQL_BLOCK',
job_action => 'begin
DW_CRF.PKG_LPS_CRF_LOAD_TRANS.sp_load_target(''LOAD_CRF'', ''LOAD_LOAN_TRAN'', CURRENT_TIMESTAMP, "NULL");
end;',
start_date => sysdate +1/24/59,
enabled => TRUE,
auto_drop => TRUE,
comments => 'LOAD LOAN TRANSACTION TABLE IN DW_CRF ' );
end;
ORA-01858: a non-numeric character was found where a numeric was expected

Hi,
The third syntax you used is correct i.e.
DW_CRF.PKG_LPS_CRF_LOAD_TRANS.sp_load_target(''LOAD_CRF'', ''LOAD_LOAN_TRAN'', CURRENT_TIMESTAMP, NULL);
Alternatively you can use
DW_CRF.PKG_LPS_CRF_LOAD_TRANS.sp_load_target(''LOAD_CRF'', ''LOAD_LOAN_TRAN'', CURRENT_TIMESTAMP, '''');
all the other calls give syntax errors that are expected. The third call is giving an application error which you will need to look into (maybe starting at "DW_CRF.PKG_LPS_CRF_LOAD_TRANS", line 958). One thing that may help clarify things is if you were to switch to naming your parameters e.g. target_name=>''LOAD_CRF'' since that helps clarify exactly what parameter is called with which value.
Hope this helps,
Ravi.

DBMS_SCHEDULER.CREATE_JOB

Hi,
I am running following script in my DB
SET SERVEROUTPUT ON SIZE 100000
Declare
v_count number ;
BEGIN
select count(*) into v_count from USER_scheduler_jobs where job_name = 'DELETE_RECORDS_IA';
if v_count > 0 then
dbms_output.put_line ('Job DELETE_RECORDS_IA Exists.. ');
DBMS_SCHEDULER.DROP_JOB (
job_name => 'DELETE_RECORDS_IA'
,force => TRUE
end if;
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'DELETE_RECORDS_IA'
,job_type => 'PLSQL_BLOCK'
,job_action => 'delete from emp2'
,repeat_interval => 'FREQ=HOURLY;INTERVAL=1'
,enabled => TRUE
it is running without error but after 16 hour when i check there is no difference in emp2 table . and when i checked from USER_scheduler_jobs table it is giving 16 time faliure of the JOB. Please suggest me how can i know why my job is failing.

I have read that document but not find the syntax for the little small action like this
You sure about that? I can see the answer to your very question right there in the create_job syntax where it describes all of the valid values for job_action depending on job_type.
And another thing - when you read the manual and get it working, you might want to think about explicitly commiting.

DBMS_SCHEDULER.CREATE_JOB executing a shell script

Hi ,
Shell script :- TEST.ksh
#!/bin/ksh
dhxmlfile=`date +"%Y-%j-%R"`
dhoriginfile= /A/XMLFirstTest.xml
dhdestinationfile=/A/B
cp $dhoriginfile $dhdestinationfile/$dhxmlfile
rm $dhoriginfile
BEGIN
DBMS_SCHEDULER.CREATE_JOB
(job_name=>'TEST.ksh',
job_type=>'EXECUTABLE',
JOB_ACTION=>'/A/TEST.ksh',
Start_date=> SYSDATE,
job_class=> 'DEFAULT_JOB_CLASS',
Enabled=> TRUE,
auto_drop=> TRUE,
Comments=> 'Run shell-script Test.ksh');
Exception
WHEN others then
DBMS_OUTPUT.PUT_LINE
(SQLCODE||SQLERRM);
end;
Getting an error :-
ORA-27369: job of type EXECUTABLE failed with exit code: 274662
STANDARD_ERROR="Oracle Scheduler error: Config file is not owned by root or is writable by group or other or extjob is not setuid and owned by root"
Can anyone help me with this

Can anyone help me with this
No - not in this forum. This forum, as the title says, is for Sql developer questions.
Please mark the question ANSWERED and repost it in the SQL and PL/SQL forum
https://community.oracle.com/community/developer/english/oracle_database/sql_and_pl_sql

Is there a maximum size limit for a single file?

I haven't been able to find a statement of the maximum size of a file. We're looking at storing several 5-10gb files in one file library.
Is it possible?
How badly would that impact performance?

maximum size of a file. All files are stored as Binary Large Objects (BLOBs), A BLOB max size is (4 gigabytes -1) * (the value of the CHUNK parameter of LOB storage). Oracle Content Services configures its LOBs to have a 32K chunk size
Note that there is a overhead by storing large files, you should compress your files if possible before storing them.
http://download-east.oracle.com/docs/cd/B25553_01/collab.1012/b25492/contentservices.htm#CACHJJGI
How badly would that impact performance?Compared to what? Oracle ASM gives you the ability to stripe your content over hundreds of physcal disks to improve the performence. http://www.oracle.com/technology/products/database/asm/index.html

DBIF_RSQL_INVALID_RSQL The maximum size of an SQL statement was exceeded

Dear,
I would appreciate a helping hand
I have a problem with a dump I could not find any note that I can help solve the problem.
A dump is appearing at various consultants which indicates the following.
>>> SELECT * FROM KNA1                     "client specified
559                  APPENDING TABLE IKNA1
560                  UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER
ST22
What happened?
    Error in the ABAP Application Program
    The current ABAP program "/1BCDWB/DBKNA1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    The SQL statement generated from the SAP Open SQL statement violates a
    restriction imposed by the underlying database system of the ABAP
    system.
    Possible error causes:
     o The maximum size of an SQL statement was exceeded.
     o The statement contains too many input variables.
     o The input data requires more space than is available.
     o ...
    You can generally find details in the system log (SM21) and in the
    developer trace of the relevant work process (ST11).
    In the case of an error, current restrictions are frequently displayed
    in the developer trace.
SQL sentence
550     if not %_l_lines is initial.
551       %_TAB2[] = %_tab2_field[].
552     endif.
553   endif.
554 ENDIF.
555 CASE ACTION.
556   WHEN 'ANZE'.
557 try.
>>> SELECT * FROM KNA1                     "client specified
559                  APPENDING TABLE IKNA1
560                  UP TO RSEUMOD-TBMAXSEL ROWS BYPASSING BUFFER
561    WHERE KUNNR IN I1
562    AND   NAME1 IN I2
563    AND   ANRED IN I3
564    AND   ERDAT IN I4
565    AND   ERNAM IN I5
566    AND   KTOKD IN I6
567    AND   STCD1 IN I7
568    AND   VBUND IN I8
569    AND   J_3GETYP IN I9
570    AND   J_3GAGDUMI IN I10
571    AND   KOKRS IN I11.
572
573   CATCH CX_SY_DYNAMIC_OSQL_SEMANTICS INTO xref.
574     IF xref->kernel_errid = 'SAPSQL_ESCAPE_WITH_POOLTABLE'.
575       message i412(mo).
576       exit.
577     ELSE.
wp trace:
D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found [dypbdatab.c 510]
D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1 Reference= >TEXT-SYS< [dypbdatab.c 430]
D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1 Reference=>TEXT-SYS< [dypbdatab.c 137]
Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1 [dypropbag.c 641]
Y *** ERROR => ... Dynpro-Field= >DISPLAY_SY_SUBRC_TEXT< [dypropbag.c 642]
Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]
D *** ERROR => dySaveDataBindingValue: Abap-Field= >TEXT-SYS< not found [dypbdatab.c 510]
D *** ERROR => dySaveDataBindingEntry: dySaveDataBindingValue() Rc=-1 Reference= >TEXT-SYS< [dypbdatab.c 430]
D *** ERROR => dySaveDataBinding: dySaveDataBindingEntry() Rc= -1 Reference=>TEXT-SYS< [dypbdatab.c 137]
Y *** ERROR => dyPbSaveDataBindingForField: dySaveDataBinding() Rc= 1 [dypropbag.c 641]
Y *** ERROR => ... Dynpro-Field= >DISPLAY_FREE_VAR_TEXT< [dypropbag.c 642]
Y *** ERROR => ... Dynpro= >SAPLSTPDA_CARRIER< >0700< [dypropbag.c 643]
I thank you in advance
If you require other information please request

Hi,
Under certain conditions, an Open SQL statement with range tables can be reformulated into a FOR ALL ENTRIES statement:
    DESCRIBE TABLE range_tab LINES lines.
    IF lines EQ 0.
      [SELECT for blank range_tab]
    ELSE.
      SELECT .. FOR ALL ENTRIES IN range_tab ..
      WHERE .. f EQ range_tab-LOW ...
      ENDSELECT.
    ENDF.
Since FOR ALL ENTRIES statements are automatically converted in accordance with the database restrictions, this solution is always met by means of a choice if the following requirements are fulfilled:
1. The statement operates on transparent tables, on database views or on a projection view on a transparent table.
2. The requirement on the range table is not negated. Moreover, the range table only contains entries with range_tab-SIGN = 'I'
and only one value ever occurs in the field range_tab OPTION.
This value is then used as an operator with operand range_tab-LOW or range_tab-HIGH.In the above example, case 'EQ range_tab-LOW' was the typical case.
3. Duplicates are removed from the result by FOR ALL ENTRIES.This must not falsify the desired result, that is, the previous Open SQL statement can be written as SELECT DISTINCT.
For the reformulation, if the range table is empty it must be handled in a different way:with FOR ALL ENTRIES, all the records would be selected here while this applies for the original query only if the WHERE clause consisted of the 'f IN range_tab' condition.
FOR ALL ENTRIES should also be used if the Open SQL statement contains several range tables.Then (probably) the most extensive of the range tables which fill the second condition is chosen as a FOR ALL ENTRIES table.
OR
What you could do in your code is,
prior to querying;
since your select options parameter is ultimately an internal range table,
1. split the select-option values into a group of say 3000 based on your limit,
2. run your query against each chunck of 3000 parameters,
3. then put together the results of each chunk.
For further reading, you might want to have a look at the Note# 13607 as the first suggestion is what I read from the note.

Maximum size of a report?

Post Author: Aravind
CA Forum: Older Products
Hi All,
I am just wondering what is the maximum size of a crystal report that is supported by Crystal Enterprises 8.5.What is the maximum size of a report whose destination can be set to email at an email ID ( assuming that the mailbox supports attachment sizes of 10MB )Thanks in advance. Regards,Aravind

Post Author: Aravind
CA Forum: Older Products
Hi Kai,Thanks for the reply.I can see that the maximum cache size has been set to 10000KB.Does this govern the number of records that is returned by a report?The idle jobs get closed in 20 minutes. Could you please provide me a pointer of where do we set up this parameter of limitting the number of records that a report returns? Thanks again,Aravind.

How to use dbms_Scheduler.Create_Job from within stored procedure?

Hello,
using 10g (10.1.0.2.0) on Windows 2000 I had problems to create scheduler jobs from within a stored procedure (see example below). What easily succeeds using anonymous blocks failed when calling from a stored procedure, due to ORA-27486. Only when I compile the procedure with invoker's rights the call to dbms_Job.Create_Job is successfull!? From my knowledge there is no difference between invoker's and definer's rights, if I compile and call with the same user, is there?
Does anyone know the reason for this behaviour or is it simply a bug?
Have a nice day.
BjÃ¶rn Hachmann
Hamburg / Germany
-- Example start.
create table t
a number(1),
b date default sysdate
create or replace procedure sched1
is
begin
dbms_scheduler.create_job(
job_name => 'TEST_JOB1',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN insert into t values (1); END;',
repeat_interval => 'freq=secondly',
enabled => TRUE
commit;
end;
create or replace procedure sched2
authid current_user
is
begin
dbms_scheduler.create_job(
job_name => 'TEST_JOB2',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN insert into t values (2); END;',
repeat_interval => 'freq=secondly',
enabled => TRUE
commit;
end;
exec sched1; -- This call fails with ORA-27486.
exec sched2; -- This call succeeds!
/* Cleanup.
exec dbms_scheduler.drop_job('TEST_JOB1', true);
exec dbms_scheduler.drop_job('TEST_JOB2', true);
drop table t;
*/

Your example code ran without problems for me on 10.1.0.3.0 so it probably is a bug.

String beginning ":OLD.DIAL_..." is too long. maximum size is 239 character

@C:\Y\trigger.sql DIM_DIAL_DIGIT ctva_ra TRG_DIM_DIAL_DIGIT1
:OLD.DIAL_DIGIT_KEY,:OLD.BU_KEY,:OLD.NOP_ID_KEY,:OLD.SDCA_LOCATION_CODE,:OLD.TARGET_REGION_DESC,:OLD.TARGET_COUNTRY_CODE,:OLD.TARGET_COUNTRY_DESC,:OLD.LDCA_NAME,:OLD.SDCA_NAME,:OLD.LDCC_X_COORD,:OLD.LDCC_Y_COORD,:OLD.SDCC_X_COORD,:OLD.SDCC_Y_COORD,:OLD.POPULATION_DATE_TIME,:OLD.ISO_COUNTRY_CODE,:OLD.HOTLIST_IND,:OLD.BLACKLIST_IND,:OLD.UPDATE_DATE_TIME,:OLD.EVENT_TYPE_KEY,:OLD.PROVIDER_DESCRIPTION,:OLD.DM_IND,:OLD.DIAL_DIGIT_OPERATOR_TYPE,:OLD.CALL_DIRECTION_KEY,:OLD.DIAL_DIGIT_DESCRIPTION,:OLD.FORCE_RI_IND,:OLD.TEST_CALL_IND DIAL_DIGIT_KEY,BU_KEY,NOP_ID_KEY,SDCA_LOCATION_CODE,TARGET_REGION_DESC,TARGET_COUNTRY_CODE,TARGET_COUNTRY_DESC,LDCA_NAME,SDCA_NAME,LDCC_X_COORD,LDCC_Y_COORD,SDCC_X_COORD,SDCC_Y_COORD,POPULATION_DATE_TIME,ISO_COUNTRY_CODE,HOTLIST_IND,BLACKLIST_IND,UPDATE_DATE_TIME,EVENT_TYPE_KEY,PROVIDER_DESCRIPTION,DM_IND,DIAL_DIGIT_OPERATOR_TYPE,CALL_DIRECTION_KEY,DIAL_DIGIT_DESCRIPTION,FORCE_RI_IND,TEST_CALL_IND;
when i am running this script it return's string beginning ":OLD.DIAL_..." is too long. maximum size is 239 characters.
how will i overcome from this situation.
i am passing parameter with .sql file

string beginning ":OLD.DIAL_..." is too long. maximum size is 239 characte. Be patient my friend....

String beginning ":OLD.DIAL_..." is too long. maximum size is 239 characte

@C:\Y\trigger.sql DIM_DIAL_DIGIT ctva_ra TRG_DIM_DIAL_DIGIT1
:OLD.DIAL_DIGIT_KEY,:OLD.BU_KEY,:OLD.NOP_ID_KEY,:OLD.SDCA_LOCATION_CODE,:OLD.TARGET_REGION_DESC,:OLD.TARGET_COUNTRY_CODE,:OLD.TARGET_COUNTRY_DESC,:OLD.LDCA_NAME,:OLD.SDCA_NAME,:OLD.LDCC_X_COORD,:OLD.LDCC_Y_COORD,:OLD.SDCC_X_COORD,:OLD.SDCC_Y_COORD,:OLD.POPULATION_DATE_TIME,:OLD.ISO_COUNTRY_CODE,:OLD.HOTLIST_IND,:OLD.BLACKLIST_IND,:OLD.UPDATE_DATE_TIME,:OLD.EVENT_TYPE_KEY,:OLD.PROVIDER_DESCRIPTION,:OLD.DM_IND,:OLD.DIAL_DIGIT_OPERATOR_TYPE,:OLD.CALL_DIRECTION_KEY,:OLD.DIAL_DIGIT_DESCRIPTION,:OLD.FORCE_RI_IND,:OLD.TEST_CALL_IND DIAL_DIGIT_KEY,BU_KEY,NOP_ID_KEY,SDCA_LOCATION_CODE,TARGET_REGION_DESC,TARGET_COUNTRY_CODE,TARGET_COUNTRY_DESC,LDCA_NAME,SDCA_NAME,LDCC_X_COORD,LDCC_Y_COORD,SDCC_X_COORD,SDCC_Y_COORD,POPULATION_DATE_TIME,ISO_COUNTRY_CODE,HOTLIST_IND,BLACKLIST_IND,UPDATE_DATE_TIME,EVENT_TYPE_KEY,PROVIDER_DESCRIPTION,DM_IND,DIAL_DIGIT_OPERATOR_TYPE,CALL_DIRECTION_KEY,DIAL_DIGIT_DESCRIPTION,FORCE_RI_IND,TEST_CALL_IND;
when i am running this script it return's string beginning ":OLD.DIAL_..." is too long. maximum size is 239 characters.
how will i overcome from this situation.
i am passing parameter with .sql file

Looks like you are trying to save the history data (with :OLD values).
If you are trying to generate a trigger at runtime, then you need a procedure which is able to loop through user_tab_columns for the given table and construct column strings for generation of triggers.
Then you can use EXECUTE IMMEDIATE to create the trigger.
Keep in mind that debugging such a procedure would be headache if you face any problems in creating the same.

Maximum size param in file channel

Hello All,
What is the parameter to mention in the sender communication channel to restrict huge files
I remember there is a paramter that can be configured in channel Maximum File Size
Can someone tell me the exact syntax for that
THanks,
Regards,
Moorthy

goto sender CC -->Parameters -->Advanced,
There is a check box "Advanced Mode".
After checking that, you will find "Maximum file size".
There you can set the maximum size of file.
-santosh.

Maximum size of dbms_scheduler.create_job job_action parameter

Similar Messages

Maybe you are looking for