not able to create new project

datability_user · Post by **datability_user** » Sat Jun 20, 2009 6:31 am

Hello guys;

we have a problem started long time ago (2+ years), which is:

We are unable to create any new project, and we are getting this error:
"Error creating a schema Some users will not have access to this schema.",
even though the user is DBA user.

we do not have any backup for UV_SCHEMA.(it was very long time).

can we copy/replace UV_SCHEMA from another server (Development), or any other place.

we appreciate any help on this.

chulett · Post by **chulett** » Sat Jun 20, 2009 7:11 am

Did you try searching for "Some users will not have access to this schema"? I got several matches, including resolved ones.

datability_user · Post by **datability_user** » Sat Jun 20, 2009 7:48 am

Thanx Graig, and yes i did but all posts talking about Admin authintications or replace from backup;

for us we are loging by admin and we do not have any backup.

thank you again Graig

ray.wurlod · Post by **ray.wurlod** » Sat Jun 20, 2009 6:41 pm

First check whether UV_SCHEMA is corrupted. It may not be, in which case there is no cause to do anything with it. In any case the six tables in the CATALOG schema are managed differently from all others.

How did you determine that the user is a DataStage DBA as you asserted?

datability_user · Post by **datability_user** » Sun Jun 21, 2009 1:19 am

Thank you Ray,

My colleague run a command suggested by you in one post:

SELECT NAME FROM UV_USERS WHERE DBAUTH = 'YES';

how can I check that UV_SCHEMA is corrupted or not? can you please advice.
[/quote]

ray.wurlod · Post by **ray.wurlod** » Sun Jun 21, 2009 5:36 pm

Any query on UV_SCHEMA that touches every page would do, or you can use UVFIXFILE or fixtool (not in fix mode). There are only as many entries in UV_SCHEMA as there are projects, so listing the entire table is only going to take one or two screens.

datability_user · Post by **datability_user** » Mon Jun 22, 2009 5:41 am

Hello Ray,

This is the output from running fixtool:

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

Start Diagnostics.
0 Errors found in physical structure.
1 Errors found in file header.
3 Errors found in file groups.
17402 Other errors found in file.

4 records processed.

17406 Errors on file.

Fixtool Completed.

can you please suggest what to do next.

ArndW · Post by **ArndW** » Mon Jun 22, 2009 8:02 am

Make a backup (better yet 2 backups) before trying to add the "-fix" option to the fixtool command. It doesn't look promising, though and the fix might truncate your UV_SCHEMA file and the system might be corrupted enough to not work any more and require a complete re-install (worst case, but it has happened to me before). The UV_SCHEMA file is central to much DataStage functionality and should be fixed.

If you do a "LIST UV_SCHEMA ID.SUP WITH EVAL '@RECORD' LIKE ..UnkownString..." what output do you get?

ray.wurlod · Post by **ray.wurlod** » Mon Jun 22, 2009 5:12 pm

I agree with Arnd. Take two backups.

That number of errors is weird - UV_SCHEMA ought only to contain very few records. You might like to involve your support provider, as there may be an issue with mismatched file units going on here.

Before trying a fix, can you add the option -level 5 to the fixtool command? This will yield information about the structure and data in the UV_SCHEMA table.

Redirect its output to a file (use tee if you want to see it on screen as well) so that the information is preserved.

datability_user · Post by **datability_user** » Wed Jun 24, 2009 5:26 am

Hello Arnd, Ray

we have ran the command and this is the output:

LIST UV_SCHEMA ID.SUP WITH EVAL '@RECORD' LIKE ..UnkownString...
@RECORD
LIST UV_SCHEMA ID.SUP WITH EVAL "@RECORD" LIKE ..UnkownString... 13:50:14
06-24-09 PAGE 1

Read operation failure. Internal file corruption detected. File must be repaired.
>
-----------------------------
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:000000000 B:000000800 W:000004004
Processing group: 2
000001000 F:00000104c B:00000004c W:000000c03
ID: 'CATALOG'
DATA: '106�/ascential/Ascential/DataStage/DSEngine/sql/catalog'
00000104c F:000001098 B:00000104c W:000000c03
ID: 'MobilyDW'
DATA: '106�/ascential/Ascential/DataStage/Projects/MobilyDW'
000001098 F:0000010e4 B:000001000 W:000000c03
ID: 'Project1'
DATA: '106�/ascential/Ascential/DataStage/Projects/Project1'
0000010e4 F:000000000 B:000001784 W:000004004
Processing group: 3
000001800 F:000000000 B:000000800 W:000004044
3 Errors found in file groups.
17402 Other errors found in file.

4 records processed.

17406 Errors on file.

Start Fixing.

An error has occurred when running.

Error: An incorrect group number has been specified
4 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:000000000 B:000000800 W:000004004
Processing group: 2
000001000 F:00000104c B:00000004c W:000004c03
00000104c F:000001098 B:00000104c W:000004c03
000001098 F:0000010e4 B:000001000 W:000004c03
0000010e4 F:000000000 B:000001784 W:000004004
Processing group: 3
000001800 F:000000000 B:000000800 W:000004044
0 Errors found in file groups.
0 Other errors found in file.

1 records processed.

2 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:000000000 B:000000800 W:000004004
Processing group: 2
000001000 F:00000104c B:00000004c W:000004c03
00000104c F:000001098 B:00000104c W:000004c03
000001098 F:0000010e4 B:000001000 W:000004c03
0000010e4 F:000000000 B:000001784 W:000004004
Processing group: 3
000001800 F:000000000 B:000000800 W:000004044
0 Errors found in file groups.
0 Other errors found in file.

1 records processed.

1 Errors on file.

Start Fixing.
0 Errors fixed.

Fixtool Completed.
$
------------------------------
When we tried to create new project we get:

DSR.ADMIN: Error creating a schemaRead operation failure. Some users will not have access to this schema.
Read operation failure. Some users will not have access to schema files.
Creating Schema "test"
Read operation failure. DataStage/SQL: Cannot write to "/ascential/Ascential/DataStage/DSEngine/sql/catalog/UV_SCHEMA".
DataStage/SQL: Could not create schema test
--------------------------------
The old error was:

DSR.ADMIN: Error creating a schemaRead operation failure. Some users will not have access to this schema.
Read operation failure. Read operation failure. Internal file corruption detected. File must be repaired.

thanks for your time and help

ArndW · Post by **ArndW** » Wed Jun 24, 2009 6:17 am

I can't quite see if you did a "-fix" or not? If you did a "-fix" could you rerun the fixtool? After a fix run could you try a TCL "LIST UV_SCHEMA" command to see if you get an error message again?

datability_user · Post by **datability_user** » Wed Jun 24, 2009 7:41 am

Hi Arnd,

Yes [-fix] was included, i have run fix again and this is the ouput from the LIST command:

>LIST UV_SCHEMA ID.SUP WITH EVAL '@RECORD' LIKE ..UnkownString...
@RECORD

0 records listed.

----------------

and this is the output for:

>LIST UV_SCHEMA

0 records listed.

Still we are not aple to create project, same error as after fix
thanx again for your help

ArndW · Post by **ArndW** » Wed Jun 24, 2009 8:32 am

The option is "-fix", not "[-fix]". If you try that it might correct the file errors.

datability_user · Post by **datability_user** » Wed Jun 24, 2009 8:43 am

Aim using [-fix] as suggested by Ray and it has fixed the DS_JOBOBJECTS hashed file.

fixtool -file AW -level 5 [ -fix ]

shall i try it as you suggested "-fix" and is there any difference between them.

Kind regards

ArndW · Post by **ArndW** » Wed Jun 24, 2009 8:56 am

Yes, the square brackets probably prevent parsing of the -fix option.