on 02-20-2019 6:27 PM
Hi all,
since some days I've been experiencing some dumps and technical problems with my ABAP Developer Edition.
As stated in note 1931223 it seems that the DB has no sufficient free space. I read along the note but I don't understand some parts.
According to note comments if I execute "isql -SNPL -Usapsa -X -w1000" following information is shown on Linux terminal:
But I don't know what to do next.
Has anybody experiencied this error in their own Dev Edition? If so, could you help me to solve mine?
I have to say that this ABAP Dev Trial is running in a VM which Virtual Disk is not yet full, so I assume I have to change DB parameters to be able to use more disk space.
Hi,
sorry for late reply. Did you ever had a look on OS Level?
Golden Rule: Read Notes complete
There you could observe that the (DATA) File grows with this command.
So something else is missing to make the DB known about this allocated Space.
So do not repeat this command, it allocate always 10Gb additional on OS Level (Check /sybase/NPL/sapdata_1)
So for me worked the following:
use master
go
disk resize name=NPL_data_001, size = 'xxG' -- size is what is being added, not the total target size of the device
go
After enter the next command from the Note the space also gets added to NPL
alter database NPL on NPL_data_001 = 'xxG'
DB size will be shown with the new size.
Good Luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It worked!! thanks Volker!!!
First of all I resized my VBox virtual disk, later I gave all the added space to the linux partition and at the very end I used the ISQL commands with ALTER command also and.... et voilà!
If anybody needs how to resize the VBox virtual disk just have a look at --> http://derekmolloy.ie/resize-a-virtualbox-disk/
As which user do you issue the isql command?
Ahh, found in the screenshot...
You need to issue this commands as sybnpl, as accessrights on OS Level avoid access as npladm...
Then the commands above should work.
Good Luck...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried with user sybnpl but the result is the same. Nothing seems to happen.
"disk resize" command seems to work without errors but if I execute sp_helpdb it seems to me that everything is as it was previously
So I assumed that I had to restart SAP but after restarting everything is as it was.
For sure I'm doing some thing wrong, but I dont know what 😞
Hi,
As which user do you issue the isql command?
As far I understood you want to extend NPL_data_001 by 10G?
Then this should work:
run isql
sp_helpdb NPL
use master
go
disk resize name=NPL_data_001, size = '10G'
go
Thats how I would do it if I had need to.
BTW: NOLOG Mode found and works as far I can see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
About your question, it seems that a log or data file can not growth further and is full.
I just started with testdrive and Sybase ASE is complete new for me. But reading the note you can expand the needed file on OS level with isql or with TA DBACOCKPIT. Last one seems not to work, at least ol of this is Grey and unaccessible. However this should be the preferred way.
So first question to answer is
The needed Info can be found in the dumps I guess.
Then extend the existing File or add space by adding a new file.
Thats what the note talks about.
Also Regular Logbackups avoid symptom 1 but normaly I would prefer a to run somehow in a Non Log / Overwrite Mode for the Logs...
Good Luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
72 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.