On commit fire triggers
Dear Friends,
I want to update the amount of the master table with the sum of all transaction records which consists of hundreds of records per a session.
I have create a temporary table, and at the point of the commit i wants to update the master table at once..
could i write a trigger for tempory table to fire on commit.
regrds
upul Indika.
To immediately answer your question, you should be able to use an after insert/update trigger. After reading the post again, I am not sure I really understand your structure. Does your master table hold the transactions and you also want to update the records with a the sum of all transactions or do you have a master table that only holds the summed values and another table (the temporary one you speak of) that holds the transactions.
As a general principle, it is not a good idea in a non-data warehouse scenario (my assumption that it is a transaction scenario) to store summed values in a table. It is much better to create a view that contains the summed amount along with any other master data. One reason for this is that you are performing the sum function each time a transaction happens but you really only need to summed amount when you actually need it (query, report, etc). Also, keeping a summed value requires you to write a bunch of code to handle an insert in the transaction table, a update to the transaction table, and a delete from the transaction table.
Similar Messages
-
Do I need to put COMMIT in DML Triggers?
I cannot find any references about it in documentation.I found this
Restrictions:
The PL/SQL block of a trigger cannot contain transaction control SQL statements (COMMIT, ROLLBACK, SAVEPOINT, and SET CONSTRAINT) if the block is executed within the same transactionAt this URL
http://technet.oracle.com/docs/products/oracle9i/doc_library/901_doc/server.901/a90125/statements_76a.htm#2063897
No - you can NOT have a commit or rollback in a trigger.
eric -
Initially copied data appears to fire triggers?
A customer installed schema A which included initially loaded rows of data. He then installed schema B with no initially loaded rows of data. He then configured Replication and started it. The intention was to have Replication initially copy data rows from A to B.
The result was that data rows in schema A copied to schema B, but it appears that the triggers in schema B fired, altering local data (dml_global_name). But the triggers have code to detect why they are firing (see sample below) and should not fire, unless "copy_rows => TRUE" does not function like a "true replicated" insert. Other than this, Replication appears to function correctly.
What gives? How do we stop the triggers on the receiving site from firing when data is initially copied? Do we have to disable triggers on schema B?
Exhibit # 1:
BEGIN
DBMS_REPCAT.CREATE_MASTER_REPOBJECT(
gname => '"GROUP2"',
type => 'TABLE',
oname => 'N_MESSAGE',
sname => '"PRODREP"',
copy_rows => TRUE,
use_existing_object => TRUE);
END;
Exhibit #2:
CREATE OR REPLACE TRIGGER n_message_UI1
BEFORE INSERT OR UPDATE ON n_message
FOR EACH ROW
DECLARE
BEGIN
IF DBMS_REPUTIL.FROM_REMOTE = FALSE THEN
SELECT global_name INTO :new.DML_Global_Name FROM GLOBAL_NAME;
SELECT sys_extract_utc(systimestamp) INTO :new.DML_Date FROM DUAL;
END IF;
END n_message_UI1;Metalink response was that a trigger can not detect the initial "copy" of data in a Replication environment. The initial "copy" is not considered a "propagation" event.
The only way to prevent a trigger from firing during the initial "copy" of data is to disable the trigger before configuring and starting replication. This means that the database must be designed to function this way.
A better solution would be for the trigger to be able to detect this situation and give the developer the means to handle it. -
Authorisation Needed to Fire Triggers in Forms 10G???
Hi everybody,
I have a Linux Red Hat AS 3.0 server with an Oracle 10g Database and Application Server. I have deployed the FMX-files there and when I enter the URL the form starts, but not one single trigger is firing.
Is this a patch problem? Is this an operating system problem?
Does anybody have any ideas?
Thank you in advance.
Hans van BaalHans - did you re-generate the FMX files on the Linux platform? FMX files are platform dependand.
Regards
Grant Ronald
Forms Product Management -
Transactional triggers and commit processing
I have only been an active member of this thread for a couple of weeks and have tried to contribute to a few postings. But I have also noticed lots of postings relating to the use of DML statements inside what I would call non commit time triggers.
What I mean here is, for example, a WHEN-BUTTON-PRESSED trigger that does inserts, updates, deletes, followed by the COMMIT_FORM procedure.
I thought it might be useful to draw attention to the possible pitfalls of this approach. I'm not saying that this approach is wrong - far from it, but sometimes it means that people aren't leveraging the functionality that you get "for free" from Forms.
By coding some DML followed by a Commit_Form, you are not getting any rollback functionality from Forms. For example:
INSERT INTO A
INSERT INTO B
COMMIT_FORM;
Let's imagine that the insert into A worked but the insert into B failed for some reason. The user gets an unhandled exception. Now imagine that the cause of the error is cleared up, and the user presses the button (or whatever the invokation action was) again, and the commit works. You will have 2 records in A and 1 in B. You may not have expected that, and without coding your own rollback/savepoint that's what you would get.
You also (1) don't get a Working... message without coding it yourself, and (2) get the "No changes to commit" message; removing this is the subject of many threads on this site.
If you have a block which is based over a table which you need to update, then all of the DML statements ought to be coded inside PRE/POST/ON INSERT/UDPATE/DELETE statements, or other Forms transactional triggers (pre-database-commit etc..). If you need to change other tables then put the DML for them inside those triggers. Then you don’t have to worry about which records the user changed – if the user didn’t touch them then Forms won’t fire the triggers. And when you call the COMMIT_FORM procedure, Forms will fire the triggers for you and if any of them fail, it will rollback back to where the COMMIT_FORM started.
An example in 1 thread I saw this morning, was a Delete button, which was to delete the current record in a multi-record block. This button performed the “DELETE FROM <table> WHERE <key=:block.key>” followed by a Commit. Then of course the block needed to be re-queried to reflect the fact that the record had gone. Using the power of Forms to simply call the DELETE_RECORD procedure would have achieved the same result without needing to requery the block. And Forms would do the delete by ROWID, the fastest way of doing it.
If you don’t have a block based over a table, then you can consider creating a dummy block which uses Transactional Triggers. Code an ON-INSERT on that block which includes the DML you want to execute. Then in the trigger initiating the commit processing you would do something like:
:DUMMY_BLOCK.ITEM1 := ‘X’;
COMMIT_FORM;
IF (NOT FORM_SUCCESS) OR :SYSTEM.FORM_STATUS != ‘QUERY’ THEN
-- the commit failed
END IF;
Then you’ll get a nice Working.. message and full rollback control.
I think the moral of what I’m trying to get across is to use the power of Forms in the way it handles the transactions. Whilst we moan about it, it is actually quite good at that!
I hope this posting is taken in a positive light, I am certainly not trying to teach anyone to “suck eggs”.
PS. I find it ironic that you were prevented from coding DML statements outside of commit time triggers, in Forms 2.3!Thank you, Kevin. Very informative.
-
FM: VHURM_HUBACKFLUSH_POST - External Commit
Dear all,
I use the FM VHURM_HUBACKFLUSH_POST in a program for production reporting. I want to backflush a bunch of HU´s corresponding to transaction MFHU (the import parameter P_SHOW_PROTOCOL is initial).
Furthermore I want to check if the backflush of all HU´s at once has been posted succesfully after the processing of the FM.
If the the backflush of all HU´s was successful make a commit if the backflush of at least one HU failed make a rollback for all HU´s to be backflushed and give the user an error message.
The issue is that the FM itself already triggers a commit internally.
Within the FM VHURM_HUBACKFLUSH_POST the FM RM_BACKFLUSH_GO is called which includes the subroutine backflush_end. This routine has the parameter am61b_ext_commit which controls if the commit should be triggered outwith the fm or not. I set this parameter in the debug mode and it worked. No backflush was executed until the commit was triggered by the calling program.
My question is now: Is it somehow possible to set this parameter outwith the FM VHURM_HUBACKFLUSH_POST already in the calling program? Any other ideas are also welcome.Hi,
After calling the FM, try putting code like below.
IF sy-subrc = 0.
SUBMIT rsconn01 WITH mode = 'INT'
WITH output = space
AND RETURN.
ENDIF. -
Our application uses Views, which are essentially mirrors of the tables to perform all updates. A GRANT ALL to PUBLIC is given to the views. These updates fire Triggers on the Tables which has worked great until we attempted to run our application at a new client running 8i on Unix. I noticed the INSTEAD_OF option on triggers for 8i, but is it a definite requirement for 8i. I can't believe the old normal trigger code now fails on 8i (by disconnecting); or is it something else. Please advise.
nullWe asked our developers and here is the answer...and a follow up question.
The INSTEAD OF is a new option on triggers to work over views. This has absolutely no impact on existing triggers on tables. If you have a view defined over a table (or set of tables) and then perform any DML over the
view, in the regular case, the DML will translate to operations on the base tables and the appropriate triggers on the base table will fire.
With the new INSTEAD OF option since Oracle8.0, you can define a trigger over
a view itself, (particular if the view is complex enough that the system cannot handle inserts/updates/deletes on the view), and the trigger body will handle the DML by firing appropriate statements.
The problem you are seeing is probably something else.
What do you mean by "disconnecting"??
Are you getting some sort of error or something when using the old triggers??
-John
null -
Potential problems with using a report to run a commit in a separate LUW.
I am working with a classic Badi within a transaction where I wanted to commit some information to a database before the commit that occurs at the end of the transaction.
Putting a commit point directly inside the BADI caused problems with cursors that were open inside the transaction, so I researched some and discovered that Report Programs can run in a separate database Logical Unit of Work (LUW).
I coded my BADI to call a report which does some database work based on input parameters, and then commits this work to the database before returning control back to the calling BADI function.
Does anyone know of any potential problems from doing this? It seems like a good way to get around restrictions on the use of commit points inside transactions, but I'm not sure if there could be potential undesired effects from doing this.
Has anyone tried this before?Hi Clay,
Yes I did it too. We faced some issues with commit when using fm HR_INFOTYPE_OPERATION . We had to enclose it in separate report which only then let us do physical change in DB.
What is to be noticed here as well is (according to SAP) that DB commit is triggered each time work process is released which happens when:
- system shows dialog message
- RFC call is executed
- new transaction is called
The above however didn't work for me in couple cases, but using separate SAP LUW solves the problem (as you already read). This happens each time:
- new report is called (SUBMIT ...),
- new transaction is called (CALL TRANSACTION ...)
- new asynchoronus RFC call is executed (CALL FUNCTION...STARTING NEW TASK).
This approach works fine for cases I met and had to overcome with such solution. So far we didn't face any issues with that. Works perfectly
Regards
Marcin -
I'm getting this error in an After Insert trigger. This trigger is calling a stored procedure which is trying to reindex using "alter index myindex rebuild". This index is on the same table as the trigger.
Also, where and how can I find information on errors returned by Oracle..
Thanks in advance, Newbee Jerry
nullHi Jerry , you can't put commit on triggers because the trigger will be part of one Transaction and this transaction won't finish until every triggers are finished. If you put a commit in one trigger you are forcing a "end of transaction " and this is not correct because you don't know if the transaction realy termineted. With this concept you can't do anything that has a commit in any trigger .
See you ,
Lourival -
Stateless Session_Bean Container_Managed does not commit SQLJ updates in 8i 8.1.7
I deployed an EJB Stateless and Container_Managed into 8i 8.1.7.
The bean contains a method with a simple SQLJ insert statement and works fine, except for no commit is triggered by the Bean Container when method call is finished.
I can see that the insert was done, because the counter for my table is increased!
So the fault has to be that there is no commit!
Why does the Bean Container not commit, as it states in the EJB Online Documentation??Is it NT or solaris 8.1.7 ?
On solaris it should have worked. On NT it wouldn't work, unless you explicitly lookup
the datasource and do a ds.getConnection(), the container doesn't know what to commit. In general, hereafter, the bean code needs to explicitly lookup datasources and call getConnection() on the datasource so that the datasource is enlisted. Using the default kprb connection isn't going to work unless you explicitly set default-enlist tag to true in the XML deployment descriptor. -
Hello friends at www.oracle.com ,
while analyzing and testing a Forms program here, I saw that, before POSTing data, the value of :SYSTEM.form_status was CHANGED (that is, database contents were changed at Forms) and, after POSTing, :SYSTEM.form_status became QUERY.
But, if POST built-in doesn't perform a database commit - so I suppose POSTed data isn't viewable to other users yet -, why does the form changes its status, if we do not have a real commit? Can't this lead the user to think data was saved (when, in fact, it's not, because POSTed data aren't committed)?
I read about POST built-in at online help, but it's still not much clear for me, so I ask your help to understand it better.
Hope I was clear - if not, please ask me.
Best regards,
Franklin Goncalves Jr.Sincere thanks for your answers. I really didn't know that POST built-in would fire triggers involved with database transactions, such as POST-COMMIT.
Isn't it better for data integrity that Forms and database be synchronized with the state of each other - that is, Forms should state its data is really committed at database? While I don't see a special reason for using POST, I'll still think POST is not so useful and avoid using it.
In some Forms programs I used a global variable, like :GLOBAL.key_commit_pressed, to determine if KEY-COMMIT was pressed (if user has committed data, that's obvious) while user is working. It doesn't seem to be a bad idea, although I still ask myself if it's really the best one.
But the most important question I have, is to know if POST built-in validates data with database - that is, integrity constraints, database triggers, and so on. I think it might fire, although I still believe the use of POST built-in can confuse both user and developer anytime.
Best regards,
Franklin Goncalves Jr. -
Mailbfr Restore = INTERNALDATE timestamp of 12:00 pm?
OS X Server 10.3.9, Xserve G5, IMAP only, no POP3.
We have been using the very excellent mailbfr v0.7.3 for backups for some time. Mail recently got hosed from a HDD corruption issue likely due to some cough third party cough RAM. Removed RAM, got OS stable, ran mailbfr -r against the backup and we were good to go. (all mail was marked unread, but that was expected)
One interesting problem. Doing a fetch shows an INTERNALDATE with the correct datestamp but a timestamp of 12:00 pm. The OS X 10.4 mail client (among others) show this as a header in the message list.
Looking at the raw source of the message, the top Received: header is shown correctly, both date and time.
All new messages received have the correct INTERNALDATE, which leads me to something in the restore process.
Is there any way to reconstruct the messages such that the INTERNALDATE time is set correctly.
I have hesitated to run mailbfr -fixdb because everything else is working fine.
Thanks,
Marc PetersonHi,
971954 wrote:
Thanks.
But how do I update it in database?
Can I run following query?
update adms_ship_fct
set asdate = trunc (asdate);
Then commit the change?
Exactly!
It might be more efficient to add a WHERE clause, so that you won't UPDATE rows (and fire triggers, and generate redo) for rows that don't need to be changed:
UPDATE adms_ship_fct
SET asdate = TRUNC (asdate)
WHERE asdate != TRUNC (asdate)
By the way, TIMESTAMP has a particular meaning in Oracle. (It's a data type similar to DATE, but with fractions of a second.) It will only cause confusion if you use "timestamp" for anything else. If you want to talk about the hours, minutes and seconds of a DATE, say "hours, minutes and seconds" or "time portion"; e.g. "I want to change the time portion of the column to 00:00:00". -
I have a multi record block that some triggers should fire and called a workflow process.I have a serial_status text item, when this status changes from OPEN to REVIEW, then the workflow process is called. I put my trigger in post_forms_commit, however, post forms commit fires whenever, you save your form ,but I want this to fire one time only, when status changes from open to review only and subsequent change should not fire again. I also put the tigger in post update, but whenever any other field is updated , post update will fire multiple times too. Please, any suggestion will be highly appreciated.
Thank you
AdeI guess what ADE is saying, after looking at the whole post over again, for like a fifth time..
is.. I think... :)
1) I want to do something only if the records are commited.
2) I want to do this do_workflow process once for each commited row if my status changed from "open" to "review".
so.. post-update isn't going to work because the commit hasnt happened yet. The data is only posted and there could be a rollback so you wouldnt want to do the do_workflow process until you are absolutely sure your data is safe and sound in the datbase. My implementatation at the top of this thread is also not going to work for the very reason Ade pointed out about the post-data-base commit on happening once.
However, Ade, you could follow my thread above using the post-data-base-commit... Call a quick expiring timer in the post-data-base commit set for like a 10th of a second. In the when-timer-expired trigger loop through every record in the block and see if the value is set to 'Y'. If the do_workflow = 'Y' for the record then do the workflow process for that record and then change the value to 'X' or something that means dont ever do this again.
If you are wondering why you need a timer in a post-database-commit it is because you cannot navigate in a post-data-base commit, but you can navigate in a when-timer-expired hence the need for a quick expiring trigger so the code executes immediately. Yeah.. this trick/hack/kludge is used quite a bit. I didnt even know about it myself until about a year ago. -
Hi All
Does any onoe know
what 's the difference between after update/insert trigger and before update/insert trigger
on database tables.Hi
The basic diffrence is
Before Update triggers before the table is updated and
After update triggers after the table is updated but
before the implicit commit fires.
therefore when you raise the application error a
implicit Rollback happens and the record is not commited.
Regards
Shajesh Nair
Deloitte.
[email protected] -
Audit Trail on R12.1 (shadow table concept)
I want to enable Audit Trail at table (column) level. Though I got response from Oracle Support but at present I am stuck on particular error. Here are the steps which I followed:
1. Apply latest Patch 12860752:R12.FND.B - Latest Audit Trail Fixes for post 12.1.3.
2. Enable Audit Trail on a table : I have set this for "PER_PEOPLE_F" tables of HR module
a. (R)System Administrator, (N) Profile -> System
Query Profile: 'AuditTrail:Activate'. Click FIND
Set it to 'Yes' at Site level.
b) Enable Audit Installations (HR)
-- Got System Admin: Security:AuditTrail:Install
-- Enable Audit Installation for HR
c) Define Audit tables and desired columns.
-- Got System Admin: Security: Audit Trail: Tables
-- Query for user table name 'PER_PEOPLE_F' and add columns on which enable trail
d) Define an Audit Group and associated tables
-- Got System Admin: Security: Audit Trail: Groups
-- Create Audit group for table defined in 'C'
e) Run Concurrent program 'AuditTrail Report for Audit Group Validation' with parameter as that of Audit Group.
f) Define an Industry Template contain Audit Group
-- Got System Admin: Security: Audit Trail Reporting: Audit Industry Template
g) Run concurrent program "AuditTrail Update Tables".
Now, I am facing challenge at point (g), as, the concurrent request "AuditTrail Update Tables" is completing with error.
And I am not able to proceed further.
****Log file shows as:****
Application Object Library: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
FNDATUPD module: AuditTrail Update Tables
Current system time is 02-APR-2013 01:02:32
----->Expand Rows
INSERT INTO FND_AUDIT_COLUMNS (TABLE_APP_ID, TABLE_ID,COLUMN_ID,STATE,SEQUENCE_ID, SCHEMA_ID, LAST_UPDATE_DATE,LAST_UPDATED_BY, LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE) VALUES ( 800, 53506, 135906, 'P', -1, 900, SYSDATE,0,0,0,SYSDATE)
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'P' WHERE T.TABLE_APP_ID = 800 AND T.TABLE_ID = 53506
commit
commit
DELETE FROM FND_AUDIT_TABLES WHERE STATE = 'X'
DELETE FROM FND_AUDIT_COLUMNS C WHERE C.STATE = 'P' AND NOT EXISTS (SELECT NULL FROM FND_AUDIT_TABLES T WHERE T.TABLE_APP_ID = C.TABLE_APP_ID AND T.TABLE_ID = C.TABLE_ID AND T.STATE !='X')
----->Update Pending Columns
----->Adding ROW_KEY
**Starts**02-APR-2013 01:02:54
**Ends**02-APR-2013 01:02:57
----->Alter Shadow Table
ALTER TABLE PER_ALL_PEOPLE_F_A ADD (FULL_NAME VARCHAR2(240))
ALTER TABLE PER_ALL_PEOPLE_F_A ADD (FULL_NAME VARCHAR2(240))
commit
commit
UPDATE FND_AUDIT_COLUMNS SET STATE = 'N' , SEQUENCE_ID = 5 WHERE TABLE_APP_ID = 800 AND SCHEMA_ID = 900 AND TABLE_ID = 53506 AND COLUMN_ID = 135906 AND STATE = 'P'
commit
commit
----->Drop Triggers
DROP TRIGGER PER_ALL_PEOPLE_F_AI
DROP TRIGGER PER_ALL_PEOPLE_F_AI
commit
DROP PROCEDURE PER_ALL_PEOPLE_F_AIP
DROP PROCEDURE PER_ALL_PEOPLE_F_AIP
commit
DROP TRIGGER PER_ALL_PEOPLE_F_AD
DROP TRIGGER PER_ALL_PEOPLE_F_AD
commit
DROP PROCEDURE PER_ALL_PEOPLE_F_ADP
DROP PROCEDURE PER_ALL_PEOPLE_F_ADP
commit
DROP TRIGGER PER_ALL_PEOPLE_F_AU
DROP TRIGGER PER_ALL_PEOPLE_F_AU
commit
DROP PROCEDURE PER_ALL_PEOPLE_F_AUP
DROP PROCEDURE PER_ALL_PEOPLE_F_AUP
commit
DROP TRIGGER PER_ALL_PEOPLE_F_AC
DROP TRIGGER PER_ALL_PEOPLE_F_AC
commit
DROP TRIGGER PER_ALL_PEOPLE_F_AH
DROP TRIGGER PER_ALL_PEOPLE_F_AH
commit
DROP TRIGGER PER_ALL_PEOPLE_F_AT
DROP TRIGGER PER_ALL_PEOPLE_F_AT
commit
----->Create Standard Triggers
CREATE OR REPLACE PROCEDURE
PER_ALL_PEOPLE_F_AIP(A0 IN DATE,A1 IN DATE,A2 IN NUMBER,JB IN DATE,JC IN VARCHAR2,JD IN VARCHAR2,E0 IN DATE,E1 IN DATE,E2 IN NUMBER,RB IN DATE,RC IN VARCHAR2,RD IN VARCHAR2 )
AS
ROWKEY number;
NXT number;
CMT number;
NUSER varchar2(100);
nls_date_fmt VARCHAR2(40);
BEGIN
select value into nls_date_fmt from v$NLS_PARAMETERS where parameter='NLS_DATE_FORMAT';
execute IMMEDIATE 'alter session set nls_date_format="MM/DD/YYYY HH24:MI:SS"';
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
ROWKEY:=(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000 MOD(NXT,100000)) * 100000 USERENV('SESSIONID');
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
INSERT INTO PER_ALL_PEOPLE_F_A
VALUES(SYSDATE,'I',NUSER,NULL,USERENV('SESSIONID'),NXT,CMT,ROWKEY,E0,E1,E2,NULL,NULL,NULL);
execute IMMEDIATE 'alter session set nls_date_format="'||nls_date_fmt||'"';
END PER_ALL_PEOPLE_F_AIP;
commit
CREATE OR REPLACE PROCEDURE
PER_ALL_PEOPLE_F_AUP (A0 IN DATE,A1 IN DATE,A2 IN NUMBER,JB IN DATE,JC IN VARCHAR2,JD IN VARCHAR2,E0 IN DATE,E1 IN DATE,E2 IN NUMBER,RB IN DATE,RC IN VARCHAR2,RD IN VARCHAR2)
AS
NXT NUMBER;
CMT NUMBER;
NUSER varchar2(100);
newtransaction_TYPE VARCHAR2(1);
newTRUE_NULLS VARCHAR2(250);
tmpPRIMCHANGE NUMBER;
nls_date_fmt VARCHAR2(40);
I0 DATE;
I1 DATE;
I2 NUMBER(10,0);
YB DATE;
YC VARCHAR2(150);
YD VARCHAR2(240);
BEGIN
select value into nls_date_fmt from v$NLS_PARAMETERS where parameter='NLS_DATE_FORMAT';
execute IMMEDIATE 'alter session set nls_date_format="MM/DD/YYYY HH24:MI:SS"';
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
SELECT 0+decode(E0,A0,0,1)+decode(E1,A1,0,1)+decode(E2,A2,0,1) into tmpPRIMCHANGE FROM SYS.DUAL;
IF tmpPRIMCHANGE>=1 THEN
SELECT decode(A0,NULL,'Y','N')
||decode(A1,NULL,'Y','N')
||decode(A2,NULL,'Y','N')
||decode(JB,NULL,'Y','N')
||decode(JC,NULL,'Y','N')
||decode(JD,NULL,'Y','N') INTO newTRUE_NULLS FROM SYS.DUAL;
IF(newTRUE_NULLS='NNNNNN')THEN
newTRUE_NULLS:=NULL;END IF;
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
INSERT INTO PER_ALL_PEOPLE_F_A
VALUES(SYSDATE,'D',NUSER,newTRUE_NULLS,
USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
A0,A1,A2,JB,JC,JD);
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
INSERT INTO PER_ALL_PEOPLE_F_A
VALUES(SYSDATE,'I',NUSER,NULL,USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
E0,E1,E2,NULL,NULL,NULL);
ELSE
SELECT DECODE(JB,RB,NULL,JB)INTO YB FROM SYS.DUAL;
SELECT DECODE(JC,RC,NULL,JC)INTO YC FROM SYS.DUAL;
SELECT DECODE(JD,RD,NULL,JD)INTO YD FROM SYS.DUAL;
SELECT decode(A0,NULL,decode(E0,NULL,'N','Y'),'N')
||decode(A1,NULL,decode(E1,NULL,'N','Y'),'N')
||decode(A2,NULL,decode(E2,NULL,'N','Y'),'N')
||decode(JB,NULL,decode(RB,NULL,'N','Y'),'N')
||decode(JC,NULL,decode(RC,NULL,'N','Y'),'N')
||decode(JD,NULL,decode(RD,NULL,'N','Y'),'N') INTO newTRUE_NULLS FROM SYS.DUAL;
IF(newTRUE_NULLS='NNNNNN')THEN newTRUE_NULLS:=NULL;END IF;
IF(newTRUE_NULLS is not NULL)OR
YB IS NOT NULL OR
YC IS NOT NULL OR
YD IS NOT NULL THEN
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
INSERT INTO PER_ALL_PEOPLE_F_A
VALUES(SYSDATE,'U',NUSER,newTRUE_NULLS,USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
E0,E1,E2,YB,YC,YD);
END IF;
END IF;
execute IMMEDIATE 'alter session set nls_date_format="'||nls_date_fmt||'"';
END PER_ALL_PEOPLE_F_AUP;
commit
CREATE OR REPLACE PROCEDURE
PER_ALL_PEOPLE_F_ADP(A0 IN DATE,A1 IN DATE,A2 IN NUMBER,JB IN DATE,JC IN VARCHAR2,JD IN VARCHAR2,E0 IN DATE,E1 IN DATE,E2 IN NUMBER,RB IN DATE,RC IN VARCHAR2,RD IN VARCHAR2)
AS
NXT NUMBER;
CMT NUMBER;
NUSER varchar2(100);
newTRUE_NULLS VARCHAR2(250);
nls_date_fmt VARCHAR2(40);
BEGIN
select value into nls_date_fmt from v$NLS_PARAMETERS where parameter='NLS_DATE_FORMAT';
execute IMMEDIATE 'alter session set nls_date_format="MM/DD/YYYY HH24:MI:SS"';
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
SELECT decode(A0,NULL,'Y','N')
||decode(A1,NULL,'Y','N')
||decode(A2,NULL,'Y','N')
||decode(JB,NULL,'Y','N')
||decode(JC,NULL,'Y','N')
||decode(JD,NULL,'Y','N') INTO newTRUE_NULLS FROM SYS.DUAL;
IF(newTRUE_NULLS='NNNNNN') THEN
newTRUE_NULLS:= NULL;
END IF;
INSERT INTO PER_ALL_PEOPLE_F_A
VALUES(SYSDATE,'D',NUSER,newTRUE_NULLS,
USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
A0,A1,A2,JB,JC,JD);
execute IMMEDIATE 'alter session set nls_date_format="'||nls_date_fmt||'"';
END PER_ALL_PEOPLE_F_ADP;
commit
CREATE OR REPLACE TRIGGER PER_ALL_PEOPLE_F_AH BEFORE INSERT ON PER_ALL_PEOPLE_F BEGIN IF fnd_global.audit_active THEN fnd_audit_pkg.audit_on := TRUE;ELSE fnd_audit_pkg.audit_on := FALSE;END IF;END;
commit
CREATE OR REPLACE TRIGGER PER_ALL_PEOPLE_F_AI AFTER INSERT ON PER_ALL_PEOPLE_F FOR EACH ROW BEGIN IF fnd_audit_pkg.audit_on THEN PER_ALL_PEOPLE_F_AIP(:old.EFFECTIVE_START_DATE,:old.EFFECTIVE_END_DATE,:old.PERSON_ID,:old.DATE_OF_BIRTH,:old.FIRST_NAME,:old.FULL_NAME,:new.EFFECTIVE_START_DATE,:new.EFFECTIVE_END_DATE,:new.PERSON_ID,:new.DATE_OF_BIRTH,:new.FIRST_NAME,:new.FULL_NAME);END IF;END;
commit
CREATE OR REPLACE TRIGGER PER_ALL_PEOPLE_F_AT BEFORE UPDATE OF EFFECTIVE_START_DATE,EFFECTIVE_END_DATE,PERSON_ID,DATE_OF_BIRTH,FIRST_NAME,FULL_NAME ON PER_ALL_PEOPLE_F BEGIN IF fnd_global.audit_active THEN fnd_audit_pkg.audit_on := TRUE;ELSE fnd_audit_pkg.audit_on := FALSE;END IF;END;
commit
CREATE OR REPLACE TRIGGER PER_ALL_PEOPLE_F_AU AFTER UPDATE OF EFFECTIVE_START_DATE,EFFECTIVE_END_DATE,PERSON_ID,DATE_OF_BIRTH,FIRST_NAME,FULL_NAME ON PER_ALL_PEOPLE_F FOR EACH ROW BEGIN IF fnd_audit_pkg.audit_on THEN PER_ALL_PEOPLE_F_AUP(:old.EFFECTIVE_START_DATE,:old.EFFECTIVE_END_DATE,:old.PERSON_ID,:old.DATE_OF_BIRTH,:old.FIRST_NAME,:old.FULL_NAME,:new.EFFECTIVE_START_DATE,:new.EFFECTIVE_END_DATE,:new.PERSON_ID,:new.DATE_OF_BIRTH,:new.FIRST_NAME,:new.FULL_NAME);END IF;END;
commit
CREATE OR REPLACE TRIGGER PER_ALL_PEOPLE_F_AC BEFORE DELETE ON PER_ALL_PEOPLE_F BEGIN IF fnd_global.audit_active THEN fnd_audit_pkg.audit_on := TRUE;ELSE fnd_audit_pkg.audit_on := FALSE;END IF;END;
commit
CREATE OR REPLACE TRIGGER PER_ALL_PEOPLE_F_AD AFTER DELETE ON PER_ALL_PEOPLE_F FOR EACH ROW BEGIN IF fnd_audit_pkg.audit_on THEN PER_ALL_PEOPLE_F_ADP(:old.EFFECTIVE_START_DATE,:old.EFFECTIVE_END_DATE,:old.PERSON_ID,:old.DATE_OF_BIRTH,:old.FIRST_NAME,:old.FULL_NAME,:new.EFFECTIVE_START_DATE,:new.EFFECTIVE_END_DATE,:new.PERSON_ID,:new.DATE_OF_BIRTH,:new.FIRST_NAME,:new.FULL_NAME);END IF;END;
commit
----->Create Views
VIEW PER_ALL_PEOPLE_F_AV1
commit
VIEW PER_ALL_PEOPLE_F_AV2
commit
VIEW PER_ALL_PEOPLE_F_AV3
commit
VIEW PER_ALL_PEOPLE_F_AV4
commit
VIEW PER_ALL_PEOPLE_F_AC1
-->EFFECTIVE_START_DATE
-->EFFECTIVE_END_DATE
-->PERSON_ID
-->DATE_OF_BIRTH
-->FIRST_NAME
-->FULL_NAME
commit
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'E' WHERE T.TABLE_ID = 53506 AND T.TABLE_APP_ID = 800 AND NOT EXISTS ( SELECT NULL FROM FND_AUDIT_COLUMNS C WHERE C.TABLE_APP_ID = T.TABLE_APP_ID AND C.TABLE_ID = T.TABLE_ID AND C.STATE = 'P' AND C.SCHEMA_ID != -1)
commit
commit
----->Delete Invalid Columns
----->Drop Triggers
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AI
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AI
commit
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AIP
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AIP
commit
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AD
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AD
commit
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_ADP
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_ADP
commit
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AU
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AU
commit
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AUP
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AUP
commit
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AC
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AC
commit
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AH
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AH
commit
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AT
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AT
commit
Cause: Table name is FND_PROFILE_OPTION_VALUE_A.
DROP VIEW FND_PROFILE_OPTION_VALUE_AV1
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV2
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV3
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV4
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV5
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV6
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV7
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV8
commit
DROP VIEW FND_PROFILE_OPTION_VALUE_AV9
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV10
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV11
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV12
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV13
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV14
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV15
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV16
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV17
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV18
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV19
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV20
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV21
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV22
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV23
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV24
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV25
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV26
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV27
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV28
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV29
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV30
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV31
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV32
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV33
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV34
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV35
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV36
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV37
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV38
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV39
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV40
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV41
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV42
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV43
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV44
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV45
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV46
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV47
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV48
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV49
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV50
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV51
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV52
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV53
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV54
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV55
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV56
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV57
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV58
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV59
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV60
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV61
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV62
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV63
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV64
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV65
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV66
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV67
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV68
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV69
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV70
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV71
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV72
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV73
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV74
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV75
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV76
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV77
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV78
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV79
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV80
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV81
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV82
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV83
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV84
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV85
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV86
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV87
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV88
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV89
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV90
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV91
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV92
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV93
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV94
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV95
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV96
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV97
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV98
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV99
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV100
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AC1
commit
----->Drop Shadow Table
DROP TABLE FND_PROFILE_OPTION_VALUE_A
ORA-00942: table or view does not exist
Error in fdasql, continuing...
/oracleferp/FERP/APPS/apps_st/appl/fnd/12.0.0/bin/FNDATUPD
Program was terminated by signal 11
Executing request completion options...
Output file size:
0
Output is not being printed because:
The print option has been disabled for this report.
Finished executing request completion options.
Concurrent request completed
Current system time is 02-APR-2013 01:03:56
Any comments/ suggestions in context of the Audit Trail query are heartily welcome !!
Regards,
S.MalikDear Hussein,
I followed the doc id: 727770.1 and as per note, I deleted the previous Audit data.
And enabled the audit trail as per document to the similar table as mentioned in the doc. with similar steps. But still the concurrent request "AuditTrail Update Tables" is completing with error. Please find below the log file for the same:
Application Object Library: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
FNDATUPD module: AuditTrail Update Tables
Current system time is 02-APR-2013 04:19:23
----->Expand Rows
INSERT INTO FND_AUDIT_COLUMNS (TABLE_APP_ID, TABLE_ID,COLUMN_ID,STATE,SEQUENCE_ID, SCHEMA_ID, LAST_UPDATE_DATE,LAST_UPDATED_BY, LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE) VALUES ( 810, 55079, 158785, 'P', -1, 900, SYSDATE,0,0,0,SYSDATE)
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'P' WHERE T.TABLE_APP_ID = 810 AND T.TABLE_ID = 55079
commit
INSERT INTO FND_AUDIT_COLUMNS (TABLE_APP_ID, TABLE_ID,COLUMN_ID,STATE,SEQUENCE_ID, SCHEMA_ID, LAST_UPDATE_DATE,LAST_UPDATED_BY, LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE) VALUES ( 810, 55079, 158787, 'P', -1, 900, SYSDATE,0,0,0,SYSDATE)
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'P' WHERE T.TABLE_APP_ID = 810 AND T.TABLE_ID = 55079
commit
INSERT INTO FND_AUDIT_COLUMNS (TABLE_APP_ID, TABLE_ID,COLUMN_ID,STATE,SEQUENCE_ID, SCHEMA_ID, LAST_UPDATE_DATE,LAST_UPDATED_BY, LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE) VALUES ( 810, 55079, 158786, 'P', -1, 900, SYSDATE,0,0,0,SYSDATE)
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'P' WHERE T.TABLE_APP_ID = 810 AND T.TABLE_ID = 55079
commit
INSERT INTO FND_AUDIT_COLUMNS (TABLE_APP_ID, TABLE_ID,COLUMN_ID,STATE,SEQUENCE_ID, SCHEMA_ID, LAST_UPDATE_DATE,LAST_UPDATED_BY, LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE) VALUES ( 810, 55079, 158790, 'P', -1, 900, SYSDATE,0,0,0,SYSDATE)
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'P' WHERE T.TABLE_APP_ID = 810 AND T.TABLE_ID = 55079
commit
commit
DELETE FROM FND_AUDIT_TABLES WHERE STATE = 'X'
DELETE FROM FND_AUDIT_COLUMNS C WHERE C.STATE = 'P' AND NOT EXISTS (SELECT NULL FROM FND_AUDIT_TABLES T WHERE T.TABLE_APP_ID = C.TABLE_APP_ID AND T.TABLE_ID = C.TABLE_ID AND T.STATE !='X')
----->Create New Table
CREATE TABLE OTA_DELEGATE_BOOKINGS_A (AUDIT_TIMESTAMP DATE NOT NULL, AUDIT_TRANSACTION_TYPE VARCHAR(1) NOT NULL, AUDIT_USER_NAME VARCHAR2(100) NOT NULL, AUDIT_TRUE_NULLS VARCHAR2(250), AUDIT_SESSION_ID NUMBER NOT NULL, AUDIT_SEQUENCE_ID NUMBER NOT NULL,AUDIT_COMMIT_ID NUMBER NOT NULL, ROW_KEY NUMBER )
commit
GRANT ALL ON OTA_DELEGATE_BOOKINGS_A to APPS
GRANT ALL ON OTA_DELEGATE_BOOKINGS_A to APPS
commit
CREATE SYNONYM OTA_DELEGATE_BOOKINGS_A for OTA.OTA_DELEGATE_BOOKINGS_A
CREATE SYNONYM OTA_DELEGATE_BOOKINGS_A for OTA.OTA_DELEGATE_BOOKINGS_A
commit
----->Adding ROW_KEY
**Starts**02-APR-2013 04:19:32
**Ends**02-APR-2013 04:19:34
----->Alter Shadow Table
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (BOOKING_ID NUMBER(9,0))
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (BOOKING_ID NUMBER(9,0))
commit
commit
DELETE FROM FND_AUDIT_COLUMNS C WHERE C.TABLE_APP_ID= 810 AND C.TABLE_ID = 55079 AND C.COLUMN_ID = 158785 AND C.SCHEMA_ID = 900
INSERT INTO FND_AUDIT_COLUMNS (TABLE_APP_ID,TABLE_ID,COLUMN_ID,STATE,SEQUENCE_ID,SCHEMA_ID,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE) VALUES ( 810, 55079, 158785, 'K', 0, 900, SYSDATE,0,0,0,SYSDATE)
commit
----->Update Pending Columns
----->Adding ROW_KEY
**Starts**02-APR-2013 04:19:36
**Ends**02-APR-2013 04:19:36
----->Alter Shadow Table
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (BOOKING_STATUS_TYPE_ID NUMBER(9,0))
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (BOOKING_STATUS_TYPE_ID NUMBER(9,0))
commit
commit
UPDATE FND_AUDIT_COLUMNS SET STATE = 'N' , SEQUENCE_ID = 1 WHERE TABLE_APP_ID = 810 AND SCHEMA_ID = 900 AND TABLE_ID = 55079 AND COLUMN_ID = 158786 AND STATE = 'P'
commit
----->Adding ROW_KEY
**Starts**02-APR-2013 04:19:37
**Ends**02-APR-2013 04:19:37
----->Alter Shadow Table
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (DELEGATE_PERSON_ID NUMBER(10,0))
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (DELEGATE_PERSON_ID NUMBER(10,0))
commit
commit
UPDATE FND_AUDIT_COLUMNS SET STATE = 'N' , SEQUENCE_ID = 2 WHERE TABLE_APP_ID = 810 AND SCHEMA_ID = 900 AND TABLE_ID = 55079 AND COLUMN_ID = 158787 AND STATE = 'P'
commit
----->Adding ROW_KEY
**Starts**02-APR-2013 04:19:37
**Ends**02-APR-2013 04:19:37
----->Alter Shadow Table
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (EVENT_ID NUMBER(9,0))
ALTER TABLE OTA_DELEGATE_BOOKINGS_A ADD (EVENT_ID NUMBER(9,0))
commit
commit
UPDATE FND_AUDIT_COLUMNS SET STATE = 'N' , SEQUENCE_ID = 3 WHERE TABLE_APP_ID = 810 AND SCHEMA_ID = 900 AND TABLE_ID = 55079 AND COLUMN_ID = 158790 AND STATE = 'P'
commit
commit
----->Drop Triggers
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AI
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AI
ORA-04080: trigger 'OTA_DELEGATE_BOOKINGS_AI' does not exist
DROP PROCEDURE OTA_DELEGATE_BOOKINGS_AIP
DROP PROCEDURE OTA_DELEGATE_BOOKINGS_AIP
ORA-04043: object OTA_DELEGATE_BOOKINGS_AIP does not exist
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AD
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AD
ORA-04080: trigger 'OTA_DELEGATE_BOOKINGS_AD' does not exist
DROP PROCEDURE OTA_DELEGATE_BOOKINGS_ADP
DROP PROCEDURE OTA_DELEGATE_BOOKINGS_ADP
ORA-04043: object OTA_DELEGATE_BOOKINGS_ADP does not exist
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AU
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AU
ORA-04080: trigger 'OTA_DELEGATE_BOOKINGS_AU' does not exist
DROP PROCEDURE OTA_DELEGATE_BOOKINGS_AUP
DROP PROCEDURE OTA_DELEGATE_BOOKINGS_AUP
ORA-04043: object OTA_DELEGATE_BOOKINGS_AUP does not exist
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AC
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AC
ORA-04080: trigger 'OTA_DELEGATE_BOOKINGS_AC' does not exist
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AH
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AH
ORA-04080: trigger 'OTA_DELEGATE_BOOKINGS_AH' does not exist
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AT
DROP TRIGGER OTA_DELEGATE_BOOKINGS_AT
ORA-04080: trigger 'OTA_DELEGATE_BOOKINGS_AT' does not exist
----->Create Standard Triggers
CREATE OR REPLACE PROCEDURE
OTA_DELEGATE_BOOKINGS_AIP(A0 IN NUMBER,JB IN NUMBER,JC IN NUMBER,JD IN NUMBER,E0 IN NUMBER,RB IN NUMBER,RC IN NUMBER,RD IN NUMBER )
AS
ROWKEY number;
NXT number;
CMT number;
NUSER varchar2(100);
nls_date_fmt VARCHAR2(40);
BEGIN
select value into nls_date_fmt from v$NLS_PARAMETERS where parameter='NLS_DATE_FORMAT';
execute IMMEDIATE 'alter session set nls_date_format="MM/DD/YYYY HH24:MI:SS"';
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
ROWKEY:=(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000 MOD(NXT,100000)) * 100000 USERENV('SESSIONID');
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
INSERT INTO OTA_DELEGATE_BOOKINGS_A
VALUES(SYSDATE,'I',NUSER,NULL,USERENV('SESSIONID'),NXT,CMT,ROWKEY,E0,NULL,NULL,NULL);
execute IMMEDIATE 'alter session set nls_date_format="'||nls_date_fmt||'"';
END OTA_DELEGATE_BOOKINGS_AIP;
commit
CREATE OR REPLACE PROCEDURE
OTA_DELEGATE_BOOKINGS_AUP (A0 IN NUMBER,JB IN NUMBER,JC IN NUMBER,JD IN NUMBER,E0 IN NUMBER,RB IN NUMBER,RC IN NUMBER,RD IN NUMBER)
AS
NXT NUMBER;
CMT NUMBER;
NUSER varchar2(100);
newtransaction_TYPE VARCHAR2(1);
newTRUE_NULLS VARCHAR2(250);
tmpPRIMCHANGE NUMBER;
nls_date_fmt VARCHAR2(40);
I0 NUMBER(9,0);
YB NUMBER(9,0);
YC NUMBER(10,0);
YD NUMBER(9,0);
BEGIN
select value into nls_date_fmt from v$NLS_PARAMETERS where parameter='NLS_DATE_FORMAT';
execute IMMEDIATE 'alter session set nls_date_format="MM/DD/YYYY HH24:MI:SS"';
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
SELECT 0+decode(E0,A0,0,1) into tmpPRIMCHANGE FROM SYS.DUAL;
IF tmpPRIMCHANGE>=1 THEN
SELECT decode(A0,NULL,'Y','N')
||decode(JB,NULL,'Y','N')
||decode(JC,NULL,'Y','N')
||decode(JD,NULL,'Y','N') INTO newTRUE_NULLS FROM SYS.DUAL;
IF(newTRUE_NULLS='NNNN')THEN
newTRUE_NULLS:=NULL;END IF;
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
INSERT INTO OTA_DELEGATE_BOOKINGS_A
VALUES(SYSDATE,'D',NUSER,newTRUE_NULLS,
USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
A0,JB,JC,JD);
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
INSERT INTO OTA_DELEGATE_BOOKINGS_A
VALUES(SYSDATE,'I',NUSER,NULL,USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
E0,NULL,NULL,NULL);
ELSE
SELECT DECODE(JB,RB,NULL,JB)INTO YB FROM SYS.DUAL;
SELECT DECODE(JC,RC,NULL,JC)INTO YC FROM SYS.DUAL;
SELECT DECODE(JD,RD,NULL,JD)INTO YD FROM SYS.DUAL;
SELECT decode(A0,NULL,decode(E0,NULL,'N','Y'),'N')
||decode(JB,NULL,decode(RB,NULL,'N','Y'),'N')
||decode(JC,NULL,decode(RC,NULL,'N','Y'),'N')
||decode(JD,NULL,decode(RD,NULL,'N','Y'),'N') INTO newTRUE_NULLS FROM SYS.DUAL;
IF(newTRUE_NULLS='NNNN')THEN newTRUE_NULLS:=NULL;END IF;
IF(newTRUE_NULLS is not NULL)OR
YB IS NOT NULL OR
YC IS NOT NULL OR
YD IS NOT NULL THEN
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
INSERT INTO OTA_DELEGATE_BOOKINGS_A
VALUES(SYSDATE,'U',NUSER,newTRUE_NULLS,USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
E0,YB,YC,YD);
END IF;
END IF;
execute IMMEDIATE 'alter session set nls_date_format="'||nls_date_fmt||'"';
END OTA_DELEGATE_BOOKINGS_AUP;
commit
CREATE OR REPLACE PROCEDURE
OTA_DELEGATE_BOOKINGS_ADP(A0 IN NUMBER,JB IN NUMBER,JC IN NUMBER,JD IN NUMBER,E0 IN NUMBER,RB IN NUMBER,RC IN NUMBER,RD IN NUMBER)
AS
NXT NUMBER;
CMT NUMBER;
NUSER varchar2(100);
newTRUE_NULLS VARCHAR2(250);
nls_date_fmt VARCHAR2(40);
BEGIN
select value into nls_date_fmt from v$NLS_PARAMETERS where parameter='NLS_DATE_FORMAT';
execute IMMEDIATE 'alter session set nls_date_format="MM/DD/YYYY HH24:MI:SS"';
NXT:=FND_AUDIT_SEQ_PKG.NXT;
CMT:=FND_AUDIT_SEQ_PKG.CMT;
NUSER:=FND_AUDIT_SEQ_PKG.USER_NAME;
SELECT decode(A0,NULL,'Y','N')
||decode(JB,NULL,'Y','N')
||decode(JC,NULL,'Y','N')
||decode(JD,NULL,'Y','N') INTO newTRUE_NULLS FROM SYS.DUAL;
IF(newTRUE_NULLS='NNNN') THEN
newTRUE_NULLS:= NULL;
END IF;
INSERT INTO OTA_DELEGATE_BOOKINGS_A
VALUES(SYSDATE,'D',NUSER,newTRUE_NULLS,
USERENV('SESSIONID'),NXT,CMT,(TO_NUMBER(TO_CHAR(SYSDATE,'YYYYMMDDHH24MISS'))*100000+MOD(NXT,100000)) * 100000 + USERENV('SESSIONID'),
A0,JB,JC,JD);
execute IMMEDIATE 'alter session set nls_date_format="'||nls_date_fmt||'"';
END OTA_DELEGATE_BOOKINGS_ADP;
commit
CREATE OR REPLACE TRIGGER OTA_DELEGATE_BOOKINGS_AH BEFORE INSERT ON OTA_DELEGATE_BOOKINGS BEGIN IF fnd_global.audit_active THEN fnd_audit_pkg.audit_on := TRUE;ELSE fnd_audit_pkg.audit_on := FALSE;END IF;END;
commit
CREATE OR REPLACE TRIGGER OTA_DELEGATE_BOOKINGS_AI AFTER INSERT ON OTA_DELEGATE_BOOKINGS FOR EACH ROW BEGIN IF fnd_audit_pkg.audit_on THEN OTA_DELEGATE_BOOKINGS_AIP(:old.BOOKING_ID,:old.BOOKING_STATUS_TYPE_ID,:old.DELEGATE_PERSON_ID,:old.EVENT_ID,:new.BOOKING_ID,:new.BOOKING_STATUS_TYPE_ID,:new.DELEGATE_PERSON_ID,:new.EVENT_ID);END IF;END;
commit
CREATE OR REPLACE TRIGGER OTA_DELEGATE_BOOKINGS_AT BEFORE UPDATE OF BOOKING_ID,BOOKING_STATUS_TYPE_ID,DELEGATE_PERSON_ID,EVENT_ID ON OTA_DELEGATE_BOOKINGS BEGIN IF fnd_global.audit_active THEN fnd_audit_pkg.audit_on := TRUE;ELSE fnd_audit_pkg.audit_on := FALSE;END IF;END;
commit
CREATE OR REPLACE TRIGGER OTA_DELEGATE_BOOKINGS_AU AFTER UPDATE OF BOOKING_ID,BOOKING_STATUS_TYPE_ID,DELEGATE_PERSON_ID,EVENT_ID ON OTA_DELEGATE_BOOKINGS FOR EACH ROW BEGIN IF fnd_audit_pkg.audit_on THEN OTA_DELEGATE_BOOKINGS_AUP(:old.BOOKING_ID,:old.BOOKING_STATUS_TYPE_ID,:old.DELEGATE_PERSON_ID,:old.EVENT_ID,:new.BOOKING_ID,:new.BOOKING_STATUS_TYPE_ID,:new.DELEGATE_PERSON_ID,:new.EVENT_ID);END IF;END;
commit
CREATE OR REPLACE TRIGGER OTA_DELEGATE_BOOKINGS_AC BEFORE DELETE ON OTA_DELEGATE_BOOKINGS BEGIN IF fnd_global.audit_active THEN fnd_audit_pkg.audit_on := TRUE;ELSE fnd_audit_pkg.audit_on := FALSE;END IF;END;
commit
CREATE OR REPLACE TRIGGER OTA_DELEGATE_BOOKINGS_AD AFTER DELETE ON OTA_DELEGATE_BOOKINGS FOR EACH ROW BEGIN IF fnd_audit_pkg.audit_on THEN OTA_DELEGATE_BOOKINGS_ADP(:old.BOOKING_ID,:old.BOOKING_STATUS_TYPE_ID,:old.DELEGATE_PERSON_ID,:old.EVENT_ID,:new.BOOKING_ID,:new.BOOKING_STATUS_TYPE_ID,:new.DELEGATE_PERSON_ID,:new.EVENT_ID);END IF;END;
commit
----->Create Views
VIEW OTA_DELEGATE_BOOKINGS_AV1
commit
VIEW OTA_DELEGATE_BOOKINGS_AV2
commit
VIEW OTA_DELEGATE_BOOKINGS_AV3
commit
VIEW OTA_DELEGATE_BOOKINGS_AV4
commit
VIEW OTA_DELEGATE_BOOKINGS_AC1
-->BOOKING_ID
-->BOOKING_STATUS_TYPE_ID
-->DELEGATE_PERSON_ID
-->EVENT_ID
commit
UPDATE FND_AUDIT_TABLES T SET T.STATE = 'E' WHERE T.TABLE_ID = 55079 AND T.TABLE_APP_ID = 810 AND NOT EXISTS ( SELECT NULL FROM FND_AUDIT_COLUMNS C WHERE C.TABLE_APP_ID = T.TABLE_APP_ID AND C.TABLE_ID = T.TABLE_ID AND C.STATE = 'P' AND C.SCHEMA_ID != -1)
commit
commit
----->Delete Invalid Columns
----->Drop Triggers
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AI
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AI
ORA-04080: trigger 'FND_PROFILE_OPTION_VALUE_AI' does not exist
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AIP
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AIP
ORA-04043: object FND_PROFILE_OPTION_VALUE_AIP does not exist
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AD
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AD
ORA-04080: trigger 'FND_PROFILE_OPTION_VALUE_AD' does not exist
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_ADP
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_ADP
ORA-04043: object FND_PROFILE_OPTION_VALUE_ADP does not exist
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AU
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AU
ORA-04080: trigger 'FND_PROFILE_OPTION_VALUE_AU' does not exist
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AUP
DROP PROCEDURE FND_PROFILE_OPTION_VALUE_AUP
ORA-04043: object FND_PROFILE_OPTION_VALUE_AUP does not exist
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AC
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AC
ORA-04080: trigger 'FND_PROFILE_OPTION_VALUE_AC' does not exist
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AH
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AH
ORA-04080: trigger 'FND_PROFILE_OPTION_VALUE_AH' does not exist
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AT
DROP TRIGGER FND_PROFILE_OPTION_VALUE_AT
ORA-04080: trigger 'FND_PROFILE_OPTION_VALUE_AT' does not exist
Cause: Table name is FND_PROFILE_OPTION_VALUE_A.
DROP VIEW FND_PROFILE_OPTION_VALUE_AV1
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV2
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV3
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV4
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV5
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV6
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV7
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV8
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV9
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV10
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV11
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV12
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV13
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV14
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV15
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV16
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV17
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV18
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV19
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV20
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV21
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV22
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV23
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV24
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV25
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV26
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV27
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV28
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV29
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV30
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV31
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV32
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV33
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV34
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV35
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV36
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV37
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV38
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV39
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV40
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV41
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV42
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV43
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV44
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV45
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV46
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV47
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV48
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV49
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV50
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV51
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV52
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV53
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV54
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV55
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV56
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV57
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV58
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV59
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV60
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV61
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV62
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV63
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV64
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV65
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV66
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV67
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV68
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV69
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV70
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV71
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV72
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV73
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV74
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV75
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV76
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV77
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV78
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV79
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV80
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV81
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV82
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV83
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV84
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV85
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV86
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV87
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV88
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV89
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV90
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV91
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV92
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV93
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV94
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV95
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV96
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV97
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV98
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV99
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AV100
ORA-00942: table or view does not exist
DROP VIEW FND_PROFILE_OPTION_VALUE_AC1
ORA-00942: table or view does not exist
----->Drop Shadow Table
DROP TABLE FND_PROFILE_OPTION_VALUE_A
ORA-00942: table or view does not exist
Error in fdasql, continuing...
/oracleferp/FERP/APPS/apps_st/appl/fnd/12.0.0/bin/FNDATUPD
Program was terminated by signal 11
Executing request completion options...
Output file size:
0
Output is not being printed because:
The print option has been disabled for this report.
Finished executing request completion options.
Concurrent request completed
Current system time is 02-APR-2013 04:19:44
Regards,
S.Malik
Maybe you are looking for
-
ITunes stopped working on Windows 7, Help please ?
I updated my iTunes to the lastest version a few days ago and whenever i open up iTunes, after a few minutes a message will appear saying "iTunes has stopped working" and then it will close down, ive tried everything, uninstall, restore iPod .. Someo
-
How to Create a wpl File in PSE 9
Can I create a Windows Media playlist (.wpl) file of pictures (with or without music) in PSE 9? I use such a file to play slide shows on my big-screen TV via my Xbox 360 extender.
-
Ok so I have updated my iPad 2 , and my brother and mother have iPhone 4 with they both updated . I have been messaging my mother fine , and she replies . She has been messaging my brother fine , and he replies . BUT , when I got to message him , it
-
Is there a tutorial/primer for working with conditional text and page numbering in book folders?
I'm ramping up on FrameMaker 9 and have been experimenting with using folders in book files. I like being able to add Frame files to the folder to organize content. But I also need to use conditional tags. In one version of my book, the entire conten
-
How to add a Totals row in a dashboard
Oracle Business Intelligence 11.1.1.6.4 Hi there gurus, I would like to know how to add a totals row at the end of a pivot table within a dashboard. Notice that the column I need to sum up is a measure column and not a dimension one. Thank a lot.