Title | Under | Posted on |
---|---|---|
Component interface Error: no rows exist for the specified keys | PeopleSoft Technical | 03/15/2019 - 3:54am |
ADD 24 months starting from current month.(peoplesoft) | PeopleSoft Functional | 07/29/2018 - 8:44pm |
TRC values dropdown | PeopleSoft Technical | 04/04/2018 - 12:54am |
how to find missing sequence in GRID and print the mising sequence number while saving through peoplecode | PeopleSoft Technical | 09/11/2017 - 4:49am |
Hi,
When you write a SQL in app engine ,the app engine does not what the SQL is doing.
It simply throws the SQL to database.
If you try inserting 1000 rows at one time and if the database finds an error inbetween the insertion due to some reason -- Duplicate rows,foreign key etc.The database will stop processing it and it will rollback all the changes.So ,you will end up inserting no rows.
There may be many ways to do it :
1.Put a do select that should process only one row at a time and put the property of that step as "Continue" on error.So the Do select will loop for 1000 times.It will skip the row which has error and will load only correct row.
2.Call a unix script within the app engine ,Using EXEC function(Synchronous Mode) and use Database procedures in the script to skip errored-out rows.You may need the help of your DBAs for this.
Please let me know should you have any questions.
Thanks
Saiyed.
----Please read the first line as----
"When you write a SQL in app engine ,the app engine does not KNOW what the SQL is doing."
Thanks
Saiyed
Hi Saiyed,
Thanks for the information.
What if we use peoplecode(using CI) for loading instead of SQL.
How do we control it in PC?
Hi,
Through CI you may skip some levels of warnings and errors but database errors can not be skipped.
The CI will fail loading it and app engine will fail.
If before hand you know what kind of errors can come .
You may load only those rows which are valid.For this you do not need a CI at all.
A SQL to get the correct set of rows is enough.
If its a case of duplicate rows being inserted then modify your SQL to filter out the duplicate rows.
If you could explain what is your requirement in more detail, i can give you a better solution...
Thanks
Saiyed.