Teradata Manager & Administrator 1

[Lysen]

Hi all,

I'm trying to get teradata manager running, but when using the tool RDBMS Setup, and entering the valid credentials it starts, but the first error is:

 5-8-2004 15:33:38  RDBMS Setup started.

__________Setting up DBCMNGR__________

Logging on to dbc as DBC...
 *** Logon successfully completed.

create database dbcmngr as perm = 10485760,
 fallback;
 *** Query failed
 *** The request to assign new PERMANENT space is invalid.    Code= 3541   Info=0   Function= 5

What to do?

Also, what's the difference between Teradata Manager and Teradata Administrator?

Does Teradata Administrator make use of the forementioned database too? When I start T.Admin and try to connect, it mentions:

The required SQL was not found in C:\program files\NCR\Teradata Administrator 6.0\sql\winddi.DEF

Hope someone can help me with this...
Kind regards,

Eli

 

[dnoeth]

Did you try to install Manager on a Demo version? If not you got a severe problem: DBC is running out of perm space, less than 10MB left.

Regarding the "SQL not found" there may be two different resons:
- you installed Administrator 6.0.0.0 on a non-english version which uses "," instead of "." as a decimal symbol. One solution is to switch your Locale settings (Control Panel -> Reginal Options).
But AFAIR you can just copy the entire [5.0] block in WinDDI.def and append it to the file as [5,0]

- you try to connect to a newer version, i.e. V2R5.1 -> Get a newer version of WinDDI...

Dieter

 

[Lysen]

Hmmm, it's not a demo version..
how can I check how much perm space is still there? It's supposed to have about 60 gigs free but maybe the space is not divided correctly between the databases...?

Well, I've got the dutch version so that , instead of a . is something I'll try first thing next monday!

Thank you, Dieter, for your reply!

 

[dnoeth]

If it's not a demo then you should try to get a newer patch of WinDDI, at least 6.0.0.1, which fixes the "SQL not found" without further modifications.


60GB free in DBC or throughout your system?

Following query calculates skew on a database level:
SELECT
DatabaseName,
MAX(MaxPerm) AS MaxPermSpace,
SUM(CurrentPerm) AS SumCurrentPerm,
CAST(((MaxCurrentPerm / (NULLIF(AvgCurrentPerm, 0))) - 1) * 100 AS DEC(5,0)) AS "%Skew",
MIN(CurrentPerm) AS MinCurrentPerm,
AVG(CurrentPerm) AS AvgCurrentPerm,
MAX(CurrentPerm) AS MaxCurrentPerm
FROM dbc.diskspace
GROUP BY 1
WHERE MaxPerm > 0
ORDER BY "%Skew" DESC;

And this one on table level, just adjust the Having clause to appropriate size and skew:

SELECT
DatabaseName,
TableName,
CAST(((MaxPerm / AvgPerm) - 1) * 100 AS DEC(5,0)) AS "%Skew",
MIN(CurrentPerm) AS MinPerm,
AVG(CurrentPerm) AS AvgPerm,
MAX(currentPerm) AS MaxPerm
FROM
dbc.TableSize
HAVING
SUM(CurrentPerm) > 100e+06
AND
"%Skew" >= 4
GROUP BY 1,2
ORDER BY "%Skew" DESC;



If dbc is skewed then the reason might be a growing dbc.AccLogTbl due to Access Logging without cleaning old data...

If dbc is not skewed then some Perm Space must be assigned to it, before it runs out of space:

Check which DB has unused Perm Space using the first query (hopefully you got a "spool_reserve" DB) and then use TD Administrator - Tools -> Move Space to assign perm to dbc.
Or use plain SQL:

If [db with free perm] is in hierarchy in the level below dbc then:
modify database [db with free perm] as perm = [new_lower_perm];

If [db with free perm] is in a deeper level:
create database dummy from [db with free perm]
as perm = xxx;
give dummy to dbc;
drop database dummy;

You'll need DROP DATABASE/USER on [db with free perm] in the first case and CREATE DATABASE on [db with free perm] and dbc in the second case, so you probably have to login as dbc.

Dieter

 

[Lysen]

I just ran the first query, and this is the result for database DBC:

	DatabaseName	MaxPermSpace	SumCurrentPerm	%Skew	MinCurrentPerm	AvgCurrentPerm	MaxCurrentPerm
	DBC                           	2.333.744.218	1.398.872.576	0	349.226.496	349.718.144	350.211.584

I don't know if I understand this correctly, but CurrentPerm is nowhere near the maxPermSpace, so how can it run out of perm space? Or is it not to be seen this way?

There are some redundant database though, which I could drop...

 

[Lysen]

oops, sorry, the above code is a bit out of sync! I'll post it again, for readability!

DatabaseName	MaxPermSpace	SumCurrentPerm	%Skew	MinCurrentPerm	AvgCurrentPerm	MaxCurrentPerm
DBC            2.333.744.218	1.398.892.032	     0	349.229.056	   349.723.008	    350.216.704

 

[dnoeth]

There's a bit less than a GB available within DBC, so 10 MB for dbcmanager shouldn't cause any problems...

Do you run SQL updates/inserts/deletes? Maybe there was a transaction running when you tried to install Manager...
Maybe some system tables (e.g. ResUsage.../AccLogTbl) have been cleaned in the mean time.

select peakperm, maxperm from dbc.diskspace
where databasename = 'dbc';
will show you if any AMP was close to it's limit.

Dieter

 

[Lysen]

PeakPerm	MaxPerm
379.228.160	2.628.394.074
379.328.512	2.628.394.074
379.961.856	2.628.394.074
379.759.104	2.628.394.074

Above is the result of your query, so no amp is/was close to it's limit!

Also, no transactions are run...

I tried to create a small db under dbc with a perm space of 1 MB, and that doesn't even work... Maybe it's some kind of bug and should I wait for the latest updates to be installed, which should be in the next few weeks...

Well... i'm stuck!
Thanks anyway for your help Dieter!

 

[dnoeth]

This sounds strange...

You log on as dbc and a "create database ... from dbc as perm = 1000000" fails with 3541 when > 2GB per AMP is free?
Then you should contact NCR.

Can you modify an existing database, e.g. "modify database systemfe as perm = a_bit_more_than_before"?


Dieter

 

[Lysen]

Nope, modifying a db/user gives me the same error.

"modify user systemfe as perm =1500000"

where the perm is only 500 Kb larger than before, but same message... 3541: The request to assign new PERMANENT space is invalid.

So I'll have to contact NCR and tell them I can't create a db under dbc while there is enough space?

Eli

 

[dnoeth]

Yes, let NCR support check this.

Dieter

 

[Lysen]

Well I contacted NCR with a report of the error, why it occurs and what I'm trying to accomplish.

I already have this problem with the 3610 error (see one of my other posts), which is a bug in our release. We'll soon get an update/upgrade on our current release, and maybe the above error is a bug too...

I'll keep you posted on the solution/workaround!

 

[Lysen]

Well, there IS a workaround!
NCR just installed it on the server and now everything seems to work as it should be!

Dieter, thanks for helping me out once again! ;-)