not able to create new project

chulett · Post by **chulett** » Wed Jun 24, 2009 9:10 am

Those square brackets are a documentation convention to denote an optional part of the command. Thus they are not an actual part of the command.

datability_user · Post by **datability_user** » Wed Jun 24, 2009 9:27 am

Hi ,

i will run it without brackets and post back the result after the weekend.i have no access on the server right now.

but if this the case, how this have done the fix for DS_JOBOBJECTS hashed file (with brackets)?

chulett · Post by **chulett** » Wed Jun 24, 2009 9:35 am

Not sure, perhaps it ignored them or wasn't bothered by them. Still you need to know what they mean as you will run into them everywhere when syntax is being documented.

datability_user · Post by **datability_user** » Tue Jun 30, 2009 3:13 am

Hello guys;

i have run the command without brackets (3 times) and this is the output:

$ fixtool -file /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA -level 5 -fix
Filename: /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA

Start Diagnostics.
0 Errors found in physical structure.
1 Errors found in file header.
Processing group: 1
000000800 F:00000084c B:00000004c W:000000c03
ID: 'CATALOG'
DATA: '106�/ascential/Ascential/DataStage/DSEngine/sql/catalog'
00000084c F:000000898 B:00000084c W:000000c03
ID: 'MobilyDW'
DATA: '106�/ascential/Ascential/DataStage/Projects/MobilyDW'
000000898 F:0000008e4 B:000000800 W:000000c03
ID: 'Project1'
DATA: '106�/ascential/Ascential/DataStage/Projects/Project1'
0000008e4 F:000000000 B:000000f84 W:000004004
3 Errors found in file groups.
181 Other errors found in file.

4 records processed.

185 Errors on file.

Start Fixing.

An error has occurred when running.

Error: An incorrect group number has been specified
3 Errors fixed.

Fixtool Completed.
$ fixtool -file /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA -level 5 -fix
Filename: /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA

Start Diagnostics.
0 Errors found in physical structure.
2 Errors found in file header.
Processing group: 1
000000800 F:00000084c B:00000004c W:000004c03
00000084c F:000000898 B:00000084c W:000004c03
000000898 F:0000008e4 B:000000800 W:000000c03
ID: 'Project1'
DATA: '106�/ascential/Ascential/DataStage/Projects/Project1'
0000008e4 F:000000000 B:000000f84 W:000004004
1 Errors found in file groups.
0 Other errors found in file.

2 records processed.

3 Errors on file.

Start Fixing.
1 Errors fixed.

Fixtool Completed.
$ fixtool -file /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA -level 5 -fix
Filename: /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA

Start Diagnostics.
0 Errors found in physical structure.
1 Errors found in file header.
Processing group: 1
000000800 F:00000084c B:00000004c W:000004c03
00000084c F:000000898 B:00000084c W:000004c03
000000898 F:0000008e4 B:000000800 W:000000c03
ID: 'Project1'
DATA: '106�/ascential/Ascential/DataStage/Projects/Project1'
0000008e4 F:000000000 B:000000f84 W:000004004
1 Errors found in file groups.
0 Other errors found in file.

2 records processed.

2 Errors on file.

Start Fixing.
0 Errors fixed.

Fixtool Completed.
$ fixtool -file /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA -level 5 -fix
Filename: /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA

Start Diagnostics.
0 Errors found in physical structure.
1 Errors found in file header.
Processing group: 1
000000800 F:00000084c B:00000004c W:000004c03
00000084c F:000000898 B:00000084c W:000004c03
000000898 F:0000008e4 B:000000800 W:000000c03
ID: 'Project1'
DATA: '106�/ascential/Ascential/DataStage/Projects/Project1'
0000008e4 F:000000000 B:000000f84 W:000004004
1 Errors found in file groups.
0 Other errors found in file.

2 records processed.

2 Errors on file.

Start Fixing.
0 Errors fixed.

Fixtool Completed.

we have only one project which is "Project1", the other one "MobilyDW" was delete long time ago (from the administrator client).

ArndW · Post by **ArndW** » Tue Jun 30, 2009 3:44 am

This means that the fixtool will be incapable of fixing all the errors in the file. I think that you are SOL in this case. The problem with the UV_SCHEMA file is that you can't play around with it they way you can with other hashed files, so the usual methods (i.e. copying contents, deleting, re-creating & reloading) won't work but will cause problems that will make the system unusable and you'll need to re-install from scratch. The projects and their contents will remain OK.
One possibility that you might try is a "RESIZE UV_SCHEMA * * *"

datability_user · Post by **datability_user** » Tue Jun 30, 2009 4:57 am

Thanx Arnd,
It seems aim not lucky,

how can i resize the UV_SCHEMA? can you give me the command or guide.

thank you a lot for your effort with me.

ArndW · Post by **ArndW** » Tue Jun 30, 2009 5:18 am

Enter into TCL and then, as shown above, type in "RESIZE UV_SCHEMA * * *"

datability_user · Post by **datability_user** » Tue Jun 30, 2009 6:32 am

Hi;

This is the output from resize:

resize /ascential/Ascential/DataStage/DSEngine/sql/catalog/"UV_SCHEMA * * *"
Usage: resize [-u] [-c] [-h | -x | -s [rows cols]]

resize /ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA * * *
Usage: resize [-u] [-c] [-h | -x | -s [rows cols]]

ArndW · Post by **ArndW** » Tue Jun 30, 2009 6:34 am

execute the command from TCL, not from a shell; i.e. "cd $DSHOME", ". ./dsenv", "uvsh", then "RESIZE UV_SCHEMA * * *"

datability_user · Post by **datability_user** » Tue Jun 30, 2009 7:07 am

Hello Arnd ;

This is the output:

RESIZE UV_SCHEMA * * *
Read operation failure. Read operation failure. RESIZE: Error on UV_SCHEMA. File not resized.

ray.wurlod · Post by **ray.wurlod** » Tue Jun 30, 2009 4:37 pm

Time to involve official support and see if they can repair your UV_SCHEMA table (hashed file) using more "deep" tools; they need someone familiar with UniVerse internals.

ArndW · Post by **ArndW** » Wed Jul 01, 2009 12:41 am

I agree with Ray, any further steps you take just run the risk of immediately corrupting the UV_SCHEMA to such an extent that you will need to re-install the engine. I think that at this stage you should just bite the bullet, choose a time when nobody is using the system, and reinstall the engine, after have done both DataStage "exports" and UNIX-level backups of your project directories.
When you re-install DataStage you can specify the path to existing project(s) and they will be made available again after installation.

datability_user · Post by **datability_user** » Wed Jul 01, 2009 2:33 am

Thank you very much all of you guys for your effort and time helping others.

we will contact IBM for this, and i will update you by the result as soon as we get it from them.

thanx again