Search results for query: *

We are running DB2 UDB v8.1 on Windows 2003. We are keep getting an error in the db2diag.log saying that "The user exit program returned an error when archiving log file S0000000.LOG from E:\psft\dev\logs\NODE0000 for database dev. The error code was 8." I checked the error code for 8, and it...

Thanks much. Hopefully they will have a solution soon.

Thanks - it will work.

In our HP-UX 11.11 box, sar data is generated in a slightly diferent name formatted file like /var/adm/sa/sa0323 - usually it is sa#dd; but in our case it is sa#mmdd. I guess it is set by the script /usr/lbin/sa/sa1. So, when I do sar -u , sar complains that /var/adm/sa/sa23 is not found. I...

I connect to my workplace through Nortel VPN client 4.1; I run Windows XP through a Linksys 4 port router (BEFSR41). I have a Verizon Business DSL with static IP address. My VPN always drops whenever I go to some web sites with an error saying "Routing Table can not be altered once the VPN...

We are experiencing performance problem with our E4000 box with A5200 array. sar -u shows that cpu %idle is below 20%. I ran a script to caputre the top information while the cpu %idle from sar -u goes below 20%. This is what it shows. I can see a 34.5% I/O wait on the system. Does it mean that...

We have some disks which we are not using in A5100 on E3000. Can we free them and use it in a different array A5200 on E4000?

What is the significance of 512. v vol01 raid5 ENABLED ACTIVE 10240000 RAID - In my case, vol01 is 4.9GB. But the length shows 10240000. I am not able to correlate it with 4.9GB.

When I do a vxprint on the volume, it brings the LENGTH in sectors. How do I convert it to get the size in MBs or GBs? For example, for one of the volumes vol01, the LEN is 10240000; how do I find convert this value to get the exact size in MBs or GBs?

In preparation to upgrade my Solaris 7 environment to Solaris 8 02/04 (using Live upgrade), I am checking the patches currently on my Solaris system. I did: /usr/sbin/patchadd -p I thought it will bring all the patches installed on my system. However, it brought a big list which only shows...

My /etc/system file has the following informtion on metadb; it shows two entries like sd:7 and ssd:39 - where does it assign these numbers to the actual disks? set md:mddb_bootlist1="sd:7:16 sd:7:1050 sd:7:2084 ssd:39:16 ssd:39:1050" set md:mddb_bootlist2="ssd:39:2084&quot...

My vfstab shows the root (/) entry like this. How do I figure out which disk the root is on: /dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 - How do I correlate the metadb information with the actual disk information.

I checked vxprint; the closest one I found is: vxprint -l vol_name|grep -i disk This brings up only the disk group, not the disks on it.

What is the command to print all the Veritas disks on a particular volume. For example, I want to find the all disk names which is part of a logical volume vol01?

I saw different releases for Solaris 8 like: Solaris 8 2/02, Solaris 8 10/01, Solaris 8 7/01 etc. What does these numbers (2/02) mean - I am assuming Solaris 8 2/02 was released on Feb 2002. Is my assumption close? I saw a release Solaris 8 2/04 - is it the latest?

We are preparing for Solaris 7 to 8 upgrade. Could someone point to me the issues list for this type of upgrade?

I want to get started on DB2 on Unix for a project. I am an experienced Oracle DBA. Can someone point to me any website links or books to get started?

I am running the tape backup and the previous errors are produced by the tape drives. But I do not know what to make from it?

Thanks for the help. Following is the part of my debug messages written on the terminal. How do I find out what the type of message it is ie, what should I add to the syslog.conf file? writemsg(5): Logging msg 'Feb 18 09:44:16 root: NetWorker Savegroup: (alert) unix_full aborted, 6 client(s)...

>first find out which facility and which level generates >the logentry -> stop syslogd and start it in > debugmode "syslogd -d" How do I start the syslogd in debug mode? I stop and start the syslog by /etc/init.d/syslg stop and /etc/init.d/syslog stop. However, this option does not...