Tag Info

New answers tagged

0

Create your statement as follows and check your data format in your table and ensure that you match the time as well (for example, |2011-01-23 14:44:36|2011-01-23 15:44:44|20140512| is the my time format in my DDL) load from myexport.del of del modified by coldel| delprioritychar dateformat=\"YYYY-MM-DD\" timestampformat=\"YYYY-MM-DD HH:MM:SS TT\" insert ...


0

just put the simple script as a resource on your RHEL Cluster. Since your on CLVMD I assume that clvmd daemon are both active on your nodes. If node one goes down RHEL Cluster will mount all active VG and LV on the other nodes as per your FAIL Over Domain and then start the database using the script provided to you. THe script should be on both server on ...


2

You can use the system catalog views. Generally speaking any view SYSCAT.xxxxxAUTH will show the authorizations for that particular area. Examples include SYSCAT.DBAUTH is authorizations at the database level. SYSCAT.ROLEAUTH is authorizations to roles. SYSCAT.INDEXAUTH is authorizations for indexes, etc.


1

Under 9.7, whichever ID creates the database is automatically granted DBADM WITH DATAACCESS WITH ACCESSCTRL and SECADM. So you should be able to log in to the databases with that ID to perform the grants you need. If this came from another environment, you may have to create the ID locally in order to get into the database. Only an ID with SECADM can grant ...


0

There doesn't seem to be a specific metric that you can use, but indirectly the high ratio of FPAGES to NPAGES and, if you have indexes, INDCARD to NDEL will tell you that there is a significant number of logically deleted rows. Unfortunately, this does not work for tables where rows are UPDATEd but not DELETEd, so I guess you will just want to run regular ...


0

This has worked for me on AIX 7.1: First, run db2ilist to find the list of instances. Run db2iset -d <instance> for each instance to remove the global registry entry. Now when you re-run db2ilist you should not see the instances, and your uninstall should work properly.


1

It is possible do this in SQL. There are really 2 problems here: Find 1 record per week for each database Calculate the average rate of consumption For the first problem, you have a couple of ways to do this: select databasename, logrecordnumber, logtimestamp from MyTable where logtimestamp > current timestamp - 42 days and ...


1

You won't get any specific answer to this question, because as you observed, it depends. The answer depends on your company's tolerance for having one DB2 instance adversely impact the performance of another's. You may be able to control or limit this impact if your AIX admins are willing to learn and set up WLM policies at the operating system level (not ...


0

Ok, this is really simplified, but hopefully helpful. DEACTIVATE is the opposite of ACTIVATE. ACTIVATE loads some of the database processes into memory to same time and performance on connections. Otherwise the first connection is where the database does this work. DEACTIVATE takes the processes out of memory. It only "completes" once everyone is logged ...



Top 50 recent answers are included