- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- MaxDB 7.5.00.26: Tables and fields cannot be remov...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
MaxDB 7.5.00.26: Tables and fields cannot be removed. How to solve?
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 05-29-2008 8:21 AM
Hi,
first of all, though it sounds similar this question is completely different to and independent from the "former question" () I posted a few hours ago. The "former question" refers to another MaxDB installation and computer where the problem mentioned below does not occur.
We have a MaxDB instance where some features do not work,
- Tables cannot be removed
- Fields of a table cannot be removed
- MaxDB odbc driver 7.5.00.26 does not work
besides of this the rest seems to be ok.
History: Originally MaxDB was installed as version 7.4. Then we migrated it to 7.5.00.26. Since (for now) some of the clients work with Win98 we use the MaxDB odbc driver 7.3 to make it possible. Unfortunately, MaxDB odbc driver 7.5.00.26 does not work on WinXP clients.
Perhaps the migration from 7.4 to 7.5.00.26 has not been done completely. Can you please point me to a info about this migration. Cannot find it any more. Perhaps something else is wrong. What can I do to solve the above mentioned "restrictions"?
Hints are very much appreciated. -- Thanks in advance.
Michael
-
All db params given by
dbmcli -d myDB -u dbm,dbm param_directgetall > maxdb_params.txtare
OK
KERNELVERSION KERNEL 7.5.0 BUILD 026-121-094-430
INSTANCE_TYPE OLTP
MCOD NO
_SERVERDB_FOR_SAP YES
_UNICODE NO
DEFAULT_CODE ASCII
DATE_TIME_FORMAT INTERNAL
CONTROLUSERID DBM
CONTROLPASSWORD
MAXLOGVOLUMES 2
MAXDATAVOLUMES 11
LOG_VOLUME_NAME_001 LOG_001
LOG_VOLUME_TYPE_001 F
LOG_VOLUME_SIZE_001 20000
DATA_VOLUME_NAME_0002 DAT_0002
DATA_VOLUME_NAME_0001 DAT_0001
DATA_VOLUME_TYPE_0002 F
DATA_VOLUME_TYPE_0001 F
DATA_VOLUME_SIZE_0002 20000
DATA_VOLUME_SIZE_0001 20000
DATA_VOLUME_MODE_0002 NORMAL
DATA_VOLUME_MODE_0001 NORMAL
DATA_VOLUME_GROUPS 1
LOG_BACKUP_TO_PIPE NO
MAXBACKUPDEVS 2
BACKUP_BLOCK_CNT 8
LOG_MIRRORED NO
MAXVOLUMES 14
_MULT_IO_BLOCK_CNT 8
_DELAY_LOGWRITER 0
LOG_IO_QUEUE 50
_RESTART_TIME 600
MAXCPU 1
MAXUSERTASKS 50
_TRANS_RGNS 8
_TAB_RGNS 8
_OMS_REGIONS 0
_OMS_RGNS 25
OMS_HEAP_LIMIT 0
OMS_HEAP_COUNT 1
OMS_HEAP_BLOCKSIZE 10000
OMS_HEAP_THRESHOLD 100
OMS_VERS_THRESHOLD 2097152
HEAP_CHECK_LEVEL 0
_ROW_RGNS 8
_MIN_SERVER_DESC 16
MAXSERVERTASKS 21
_MAXTRANS 292
MAXLOCKS 2920
_LOCK_SUPPLY_BLOCK 100
DEADLOCK_DETECTION 4
SESSION_TIMEOUT 900
OMS_STREAM_TIMEOUT 30
REQUEST_TIMEOUT 5000
_IOPROCS_PER_DEV 2
_IOPROCS_FOR_PRIO 0
_USE_IOPROCS_ONLY NO
_IOPROCS_SWITCH 2
LRU_FOR_SCAN NO
_PAGE_SIZE 8192
_PACKET_SIZE 36864
_MINREPLY_SIZE 4096
_MBLOCK_DATA_SIZE 32768
_MBLOCK_QUAL_SIZE 16384
_MBLOCK_STACK_SIZE 16384
_MBLOCK_STRAT_SIZE 8192
_WORKSTACK_SIZE 8192
_WORKDATA_SIZE 8192
_CAT_CACHE_MINSIZE 262144
CAT_CACHE_SUPPLY 1632
INIT_ALLOCATORSIZE 221184
ALLOW_MULTIPLE_SERVERTASK_UKTS NO
_TASKCLUSTER_01 tw;al;ut;2000*sv,100*bup;10*ev,10*gc;
_TASKCLUSTER_02 ti,100*dw;30000*us;
_TASKCLUSTER_03 compress
_DYN_TASK_STACK NO
_MP_RGN_QUEUE YES
_MP_RGN_DIRTY_READ NO
_MP_RGN_BUSY_WAIT NO
_MP_DISP_LOOPS 2
_MP_DISP_PRIO NO
XP_MP_RGN_LOOP 0
MP_RGN_LOOP 0
_MP_RGN_PRIO NO
MAXRGN_REQUEST 300
_PRIO_BASE_U2U 100
_PRIO_BASE_IOC 80
_PRIO_BASE_RAV 80
_PRIO_BASE_REX 40
_PRIO_BASE_COM 10
_PRIO_FACTOR 80
_DELAY_COMMIT NO
_SVP_1_CONV_FLUSH NO
_MAXGARBAGE_COLL 0
_MAXTASK_STACK 400
MAX_SERVERTASK_STACK 100
MAX_SPECIALTASK_STACK 100
_DW_IO_AREA_SIZE 50
_DW_IO_AREA_FLUSH 50
FBM_VOLUME_COMPRESSION 50
FBM_VOLUME_BALANCE 10
_FBM_LOW_IO_RATE 10
CACHE_SIZE 10000
_DW_LRU_TAIL_FLUSH 25
XP_DATA_CACHE_RGNS 0
_DATA_CACHE_RGNS 8
XP_CONVERTER_REGIONS 0
CONVERTER_REGIONS 8
XP_MAXPAGER 0
MAXPAGER 11
SEQUENCE_CACHE 1
_IDXFILE_LIST_SIZE 2048
_SERVER_DESC_CACHE 74
_SERVER_CMD_CACHE 22
VOLUMENO_BIT_COUNT 8
OPTIM_MAX_MERGE 500
OPTIM_INV_ONLY YES
OPTIM_CACHE NO
OPTIM_JOIN_FETCH 0
JOIN_SEARCH_LEVEL 0
JOIN_MAXTAB_LEVEL4 16
JOIN_MAXTAB_LEVEL9 5
_READAHEAD_BLOBS 25
RUNDIRECTORY /var/opt/sdb/data/wrk/EVERW_B6
OPMSG1 /dev/console
OPMSG2 /dev/null
_KERNELDIAGFILE knldiag
KERNELDIAGSIZE 800
_EVENTFILE knldiag.evt
_EVENTSIZE 0
_MAXEVENTTASKS 1
_MAXEVENTS 100
_KERNELTRACEFILE knltrace
TRACE_PAGES_TI 2
TRACE_PAGES_GC 0
TRACE_PAGES_LW 5
TRACE_PAGES_PG 3
TRACE_PAGES_US 10
TRACE_PAGES_UT 5
TRACE_PAGES_SV 5
TRACE_PAGES_EV 2
TRACE_PAGES_BUP 0
KERNELTRACESIZE 653
EXTERNAL_DUMP_REQUEST NO
_AK_DUMP_ALLOWED YES
_KERNELDUMPFILE knldump
_RTEDUMPFILE rtedump
_UTILITY_PROTFILE dbm.utl
UTILITY_PROTSIZE 100
_BACKUP_HISTFILE dbm.knl
_BACKUP_MED_DEF dbm.mdf
_MAX_MESSAGE_FILES 0
_EVENT_ALIVE_CYCLE 0
_SHAREDDYNDATA 10280
_SHAREDDYNPOOL 3658
_SHMKERNEL 91663
DIAG_HISTORY_NUM 2
DIAG_HISTORY_PATH /var/opt/sdb/data/wrk/EVERW_B6/DIAGHISTORY
_DIAG_SEM 1
SHOW_MAX_STACK_USE NO
LOG_SEGMENT_SIZE 6666
SUPPRESS_CORE YES
FORMATTING_MODE PARALLEL
FORMAT_DATAVOLUME YES
LOAD_BALANCING_CHK 0
LOAD_BALANCING_DIF 10
LOAD_BALANCING_EQ 5
HS_STORAGE_DLL libhsscopy
HS_SYNC_INTERVAL 50
USE_OPEN_DIRECT NO
SYMBOL_DEMANGLING NO
EXPAND_COM_TRACE NO
OPTIMIZE_OPERATOR_JOIN_COSTFUNC YES
OPTIMIZE_JOIN_PARALLEL_SERVERS 0
OPTIMIZE_JOIN_OPERATOR_SORT YES
OPTIMIZE_JOIN_OUTER YES
JOIN_OPERATOR_IMPLEMENTATION IMPROVED
JOIN_TABLEBUFFER 128
OPTIMIZE_FETCH_REVERSE YES
SET_VOLUME_LOCK YES
SHAREDSQL NO
SHAREDSQL_EXPECTEDSTATEMENTCOUNT 1500
SHAREDSQL_COMMANDCACHESIZE 32768
MEMORY_ALLOCATION_LIMIT 0
USE_SYSTEM_PAGE_CACHE YES
USE_COROUTINES YES
USE_STACK_ON_STACK YES
USE_UCONTEXT YES
MIN_RETENTION_TIME 60
MAX_RETENTION_TIME 480
MAX_SINGLE_HASHTABLE_SIZE 512
MAX_HASHTABLE_MEMORY 5120
HASHED_RESULTSET NO
HASHED_RESULTSET_CACHESIZE 262144
AUTO_RECREATE_BAD_INDEXES NO
LOCAL_REDO_LOG_BUFFER_SIZE 0
FORBID_LOAD_BALANCING YES
SIMULATE_VECTORIO IF_OPEN_DIRECT_OR_RAW_DEVICEEdited by: Michael Poetzsch on May 29, 2008 9:23 AM
- SAP Managed Tags:
- SAP MaxDB
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Michael,
how did you do the Migration?
Did you use SDBUPD? If so, are there any errors in the logfile SDBUPD wrote (look into /sapdb/data/wrk)
Had the systemtables been reloaded afterwards via load_systab?
What are the error messages you see when you try to drop a table/column?
What exactly is the problem with the ODBC driver?
KR Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Lars,
>
> Hi Michael,
>
> how did you do the Migration?
> Did you use SDBUPD? If so, are there any errors in the logfile SDBUPD wrote (look into /sapdb/data/wrk)
> Had the systemtables been reloaded afterwards via load_systab?
> What are the error messages you see when you try to drop a table/column?
The person who did it unfortunately could not remember whether "sdbupd" has been used or not. The install log is available:
/var/opt/sdb/data/wrk/MaxDBSoftware_install-19.06.2005-11.16.log
but there is no other log file in this directory. The install sources (where sdbupd is located) do still exist:
/usr/local/lib/maxdb-all-linux-32bit-i386-7_5_00_26
Dropping a table or column causes the following error messages
DROP TABLE MY_TABLE1
=> Error:
Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed
General error;-28534 POS(1) Package must be recreated:N
DROP TABLE MY_TABLE1
ALTER TABLE MY_TABLE1 DROP ("MYCOL7")
=> Error:
Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed
General error;-28534 POS(1) Package must be recreated:N
ALTER TABLE MY_TABLE1 DROP ("MYCOL7")Could you please tell me the remaining needed steps in detail, or point me to a document which explains it?
>
What exactly is the problem with the ODBC driver?
>
> KR Lars
I checked it myself yesterday. I was able to connect to the MaxDB db version 7.5.00.26 by the MaxDB odbc driver 7.5.00.26.
Kind regards
Michael
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Michael,
hmm... sounds as if somebody just installed the software and then ... did what? hmm...
The next step I would try is: perform a load_systab.
Make sure you've a complete backup before that - just to be on the safe side.
BTW: could you post the dbm.prt? We should see how this instance got created there.
KR Lars
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
... will give "load_systab" a try (Since I have to go to the customer, it will take a few days until I can check it).
Kind regards
Michael
dbm.prt:
------------------------------------------------------------------------------
Date Time TID(hex) Typ MsgID Label Message
------------------------------------------------------------------------------
2005-06-23 13:59:54 0x000023e9 0 DBM command db_cold
2005-06-23 14:08:20 0x000023e9 0 DBM command medium_getall
2005-06-23 14:08:20 0x000023e9 ERR -24986 DBM ERR_NOMEDIA: media file not found
2005-06-23 14:09:09 0x000023e9 0 DBM command medium_getall
2005-06-23 14:09:09 0x000023e9 ERR -24986 DBM ERR_NOMEDIA: media file not found
2005-06-23 14:09:09 0x000023e9 0 DBM command medium_put "bu_20060523_1514_init" "BU_20050623_1319_compl" FILE DATA 0 8 NO NO ""
2005-06-23 14:10:07 0x000023e9 0 DBM command medium_put "bu_20060523_1514_init" "BU_20050623_1319_compl" FILE DATA 0 8 NO NO ""
2005-06-23 14:10:16 0x000023e9 0 DBM command db_activate_req
2005-06-23 14:10:27 0x000023e9 0 DBM command backup_reply_receive
2005-06-23 14:10:36 0x000023e9 0 DBM command db_warm
2005-06-23 14:10:37 0x000023e9 0 DBM command dbm_configset -raw
2005-06-23 14:59:08 0x000023e9 0 DBM command db_cold
2005-06-23 14:59:19 0x000023e9 0 DBM command db_stop
2005-06-23 15:02:50 0x00002adf 0 DBM command db_offline
2005-06-23 15:50:45 0x00001ad5 0 DBM command db_warm
2005-06-27 13:28:22 0x000040db 0 DBM command db_offline
2005-06-27 15:14:50 0x00001c00 0 DBM command db_warm
2005-06-27 15:29:41 0x00001dc3 0 DBM command db_cold
2005-06-27 15:30:45 0x00001dc3 0 DBM command medium_put "bu_20050627_1143_ini" "BU_20050627_1143_compl" FILE DATA 0 8 NO NO ""
2005-06-27 15:30:57 0x00001dc3 0 DBM command recover_req "bu_20050627_1143_ini" DATA
2005-06-27 15:30:58 0x00001dc3 0 DBM command backup_reply_receive
2005-06-27 15:32:08 0x00001dc3 0 DBM command db_activate_req
2005-06-27 15:32:20 0x00001dc3 0 DBM command backup_reply_receive
2005-06-27 15:32:29 0x00001dc3 0 DBM command db_warm
2005-06-27 15:32:30 0x00001dc3 0 DBM command dbm_configset -raw
2005-06-27 16:30:28 0x00001dc3 0 DBM command param_getdevspace
2005-06-27 16:30:28 0x00001dc3 ERR -24996 DBM ERR_PARAM: wrong parameters
2005-07-05 09:51:41 0x00001dc3 0 DBM command db_cold
2005-07-05 10:36:46 0x000045fe 0 DBM command db_warm
2005-07-05 10:48:00 0x00004a45 0 DBM command db_offline
2005-07-05 10:49:07 0x00004acf 0 DBM command db_warm
2005-07-05 11:08:51 0x00001b22 0 DBM command db_warm
2005-07-05 11:19:30 0x00001ba2 0 DBM command db_offline
2005-07-05 11:19:38 0x00001bbf 0 DBM command db_warm
2005-07-05 11:22:04 0x00001c23 0 DBM command db_offline
2005-07-05 11:41:49 0x00002101 0 DBM command db_warm
2005-07-05 11:44:06 0x0000213c 0 DBM command db_offline
2005-07-05 11:44:28 0x00002158 0 DBM command db_warm
2005-07-05 11:54:24 0x000022c5 0 DBM command db_offline
2005-07-05 11:55:20 0x0000113f 0 DBM command db_warm
2005-07-05 11:57:22 0x00001af5 0 DBM command db_cold
2005-07-05 11:59:10 0x00001af5 0 DBM command medium_put "BU_20050705_0914_init" "BU_20050705_0914_compl" FILE DATA 0 8 NO NO ""
2005-07-05 11:59:21 0x00001af5 0 DBM command db_activate_req
2005-07-05 11:59:34 0x00001af5 0 DBM command backup_reply_receive
2005-07-05 11:59:45 0x00001af5 0 DBM command db_warm
2005-07-05 11:59:46 0x00001af5 0 DBM command dbm_configset -raw
2005-07-08 09:16:37 0x00001f21 0 DBM command db_offline
2005-07-08 09:24:30 0x0000147e 0 DBM command db_warm
2005-07-08 09:44:17 0x00001f90 0 DBM command db_offline
2005-07-08 09:45:22 0x0000140a 0 DBM command db_warm
2005-07-08 11:04:12 0x000022f3 0 DBM command db_offline
2005-07-08 11:17:07 0x00001130 0 DBM command db_warm
2005-07-08 12:20:36 0x00001b9d 0 DBM command db_cold
2005-07-08 12:21:12 0x00001b9d 0 DBM command medium_put "BU_20050708_0742_init" "BU_20050708_0742_compl" FILE DATA 0 8 NO NO ""
2005-07-08 12:21:19 0x00001b9d 0 DBM command db_activate_req
2005-07-08 12:21:30 0x00001b9d 0 DBM command backup_reply_receive
2005-07-08 12:21:34 0x00001b9d 0 DBM command db_warm
2005-07-08 12:21:36 0x00001b9d 0 DBM command dbm_configset -raw
...- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Answers (0)
- Configuring SAP CI/CD pipeline for Deploying ReactJS application in Cloud Foundry in Technology Q&A
- sap.ui.RichTextEditor conflicting with sap cap application validation message popup in Technology Q&A
- Best practice to connect to multiple databases (Crystal Report) in Technology Q&A
- ABAP2XLSX problem downloading file in Technology Q&A
- Cap list output from query not working in Technology Q&A
| User | Count |
|---|---|
| 86 | |
| 10 | |
| 10 | |
| 9 | |
| 7 | |
| 7 | |
| 6 | |
| 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.