IDS data extract jobs from cron without resource permissions
Ver: INFORMIX-OnLine Version 7.23.UC11 UNIX: 11.x Ok, we have a logged database and do our bulk data manipulation and extract jobs via cron. One technique is to build a permanent table of key identifiers for the duration of the job, the drop the table when we're done. The Sr. SysAdmin now has a new non-root crontab that doesn't have resource permissions. Any ideas on a better way to do business than by temporary adds of permanent type tables?? We can do all the temp adds we want, but they are only accessible from current SQL and then only last for the duration of the current SQL. I want to use that table for several SQLs. Rob
Konikoff, Rob wrote: > Ver: INFORMIX-OnLine Version 7.23.UC11 > UNIX: 11.x > > Ok, we have a logged database and do our bulk data manipulation and extract jobs > via cron. One technique is to build a permanent table of key identifiers for > the duration of the job, the drop the table when we're done. The Sr. SysAdmin > now has a new non-root crontab that doesn't have resource permissions. > > Any ideas on a better way to do business than by temporary adds of permanent > type tables?? > > We can do all the temp adds we want, but they are only accessible from current > SQL and then only last for the duration of the current SQL. I want to use that > table for several SQLs. Unless you want to upgrade to IDS 9.40 or 10.00 and use external tables to load the keys into a file accessible to IDS as if it were a table, no. What you are doing is probably best. Just grant resource perms to the cron user id. Art S. Kagel
Konikoff, Rob wrote: > Ver: INFORMIX-OnLine Version 7.23.UC11 > UNIX: 11.x > > Ok, we have a logged database and do our bulk data manipulation and extract jobs > via cron. One technique is to build a permanent table of key identifiers for > the duration of the job, the drop the table when we're done. The Sr. SysAdmin > now has a new non-root crontab that doesn't have resource permissions. > > Any ideas on a better way to do business than by temporary adds of permanent > type tables?? > > We can do all the temp adds we want, but they are only accessible from current > SQL and then only last for the duration of the current SQL. I want to use that > table for several SQLs. Unless you want to upgrade to IDS 9.40 or 10.00 and use external tables to load the keys into a file accessible to IDS as if it were a table, no. What you are doing is probably best. Just grant resource perms to the cron user id. Art S. Kagel