from a programmer view even the job is gonna be run daily you should always assume that there are possibility of not running the job because of any events that could happen
I once got a ORA-04030 in a server with 20gb physical memory
Printable View
from a programmer view even the job is gonna be run daily you should always assume that there are possibility of not running the job because of any events that could happen
I once got a ORA-04030 in a server with 20gb physical memory
But that comes under the perview of monitoring processes and database.We have people recruted especially for that.Quote:
Originally posted by pando
from a programmer view even the job is gonna be run daily you should always assume that there are possibility of not running the job because of any events that could happen
With 4 million records?Quote:
Originally posted by pando
I once got a ORA-04030 in a server with 20gb physical memory
Uhm when I got ORA-04030 i think the number of records I was dealing was around 2 million or so. The memory per process is determined by the OS anyway (AFIAK)
Regarding the process not running, I am currently in a OLTP migration process which affects DWH and Data Marts. Quite a few ETL process for example are being stopped for 1 week or more until the OLTP application is migrated fully (old app and new app running in parallel), in this situation for example the processes are hold on purpose, if one of processes is using collections (without controlling number of elements per array) it might not work when over a week data must be transferred to DWH/Data Marts and thing would screwed up and that´s why I said from a programmer view you should always make sure that your program can deal with ANY amount of data
I agree Load testing is certainly a requirement.Mine is not that complex although.Quote:
Originally posted by pando
Uhm when I got ORA-04030 i think the number of records I was dealing was around 2 million or so. The memory per process is determined by the OS anyway (AFIAK)
Regarding the process not running, I am currently in a OLTP migration process which affects DWH and Data Marts. Quite a few ETL process for example are being stopped for 1 week or more until the OLTP application is migrated fully (old app and new app running in parallel), in this situation for example the processes are hold on purpose, if one of processes is using collections (without controlling number of elements per array) it might not work when over a week data must be transferred to DWH/Data Marts and thing would screwed up and that´s why I said from a programmer view you should always make sure that your program can deal with ANY amount of data