Run-time error '9': Subscript out of range.

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
elavenil
Premium Member
Premium Member
Posts: 467
Joined: Thu Jan 31, 2002 10:20 pm
Location: Singapore

Run-time error '9': Subscript out of range.

Post by elavenil »

Hi DS Gurus,

While running a job, which produced lot of warnings and it issued 'Run-time error '9': Subscript out of range'. Logged into administrator and cleared log using CLEAR RT_LOGxxx.

Encountered the same error 'Run-time error '9': Subscript out of range', while logging into designer but i am able to login to DS administrator.

Could someone throw some light on this?

Note: Able to access other projects in the same server.

Regards
Elavenil
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

If you get an error like that simply by logging on, I would think you have some kind of corruption in the project / XMETA database and you should be contacting your official support provider for help.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I think this is a Windows (Visual Basic) error. Can you log in with Director client?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
rameshrr3
Premium Member
Premium Member
Posts: 609
Joined: Mon May 10, 2004 3:32 am
Location: BRENTWOOD, TN

Post by rameshrr3 »

Thie is not just an Xmeta error. I get it with datastage 7.5 client also. Its a visual basic error with some sort of repository corruption issue that interferes with the working of datastage clients.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

So... would the solution then be a complete reinstall of the client?

I also be curious if this happens to other people or just the OP. The latter would seem to confirm the need to reinstall the client.
-craig

"You can never have too many knives" -- Logan Nine Fingers
rameshrr3
Premium Member
Premium Member
Posts: 609
Joined: Mon May 10, 2004 3:32 am
Location: BRENTWOOD, TN

Post by rameshrr3 »

Haven't reinstalled the 7.51 A client , Just open director witha different job category showing; as it would require re installing v 8.7 client and a multi client manager - not enough time to go through that pain right now. A search on IBM site (alt+w) may help .
The OP can attempt to open a different job category.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

chulett wrote:I also be curious if this happens to other people or just the OP.
It may not have been obvious, but I meant other people in the OP's office.
-craig

"You can never have too many knives" -- Logan Nine Fingers
elavenil
Premium Member
Premium Member
Posts: 467
Joined: Thu Jan 31, 2002 10:20 pm
Location: Singapore

Post by elavenil »

Thanks everyone for your responses.

Hi Ray,

I am getting the same error when i login to Director client as well.

Hi Ramesh,

Tried enabling the trace by following IBM recommendation in the URL but it did not help. I could not make out anything based on the entries available in the trace files.

Hi Chullet,

Would like to perform reinstallation of client as a last resort.

Appreciate your help.

Regards
Elavenil
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Help us out with one thing - does this error happen for other developers in your office or just you?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Might it be possible that you installed some other software (or had software installed/updated automatically) on your client PC? This might have overwritten DLLs and thus caused your problems. A client re-installation would solve your problem if that were the cause.
elavenil
Premium Member
Premium Member
Posts: 467
Joined: Thu Jan 31, 2002 10:20 pm
Location: Singapore

Post by elavenil »

Hi Chullet,

This issue occurs for everyone who logs into this project.

Hi ArndW,

There is no other SW installation on this server.

Still trying to figure out the cause of this issue. Few developers created jobs on this project but no backup of them so recovery of those jobs are very critical.

Regards
Elavenil
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

elavenil wrote:This issue occurs for everyone who logs into this project.
That's an important bit of information and rules out the whole client-side possibility. Rather than trying to "figure this out" I'd suggest getting this in front of your official support provider if you haven't already.
-craig

"You can never have too many knives" -- Logan Nine Fingers
elavenil
Premium Member
Premium Member
Posts: 467
Joined: Thu Jan 31, 2002 10:20 pm
Location: Singapore

Post by elavenil »

Hi Ramesh,

Checked in 'C:\winnt\system32' of the client machines and both files exist in the directory.

I think that this is not related to client as we are able to login to other projects and only this project is the issue.

Checked in the server and do not see any core dumps.

As recommended, ISAlite can be run to identify any symptoms of this issue.

Regards
Elavenil
Post Reply