We try to implement ASM database in oracle linux 7 platform
First we installed oracle grid and database installation 11.2.0.1 completed successfully .
At the time of database creation after reached 86 % is not started , but database is created .
[grid#localhost grid]$ /u01/app/grid/product/11.2.0/grid/bin/srvctl status database -d ram
Database is not running.
[grid#localhost grid]$ /u01/app/grid/product/11.2.0/grid/bin/srvctl start database -d ram
PRCR-1079: Failed to start resource ora.ram.db
CRS-5017: The resource action "ora.ram.db start" encountered the following error:
ORA-01078: failure in processing system parameters
. For details refer to "(:CLSN00107:)" in "/u01/app/grid/product/11.2.0/grid/log/localhost/agent/ohasd/oraagent_grid/oraagent_grid.log".
CRS-2674: Start of 'ora.ram.db' on 'localhost' failed
I Checked below link and proceed the steps:
https://levipereira.wordpress.com/2016/09/01/prcr-1079-crs-5017-ora-01017-dbca-fails-to-create-a-database-in-oracle-restart-environment-12c/
but still not able to start a ASM database
contents of oraagent_grid.log
Oracle Database 11g Clusterware Release 11.2.0.4.0 - Production Copyright 1996, 2011 Oracle. All rights reserved.
2018-07-16 21:26:42.215: [ora.LISTENER.lsnr][3174700800]{0:0:2} [check] execCmd ret = 0
2018-07-16 21:27:09.869: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115784
2018-07-16 21:27:10.771: [ora.evmd][3174700800]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:27:10.771: [ora.evmd][3174700800]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:27:10.771: [ora.evmd][3174700800]{0:0:2} [check] Deep check returned 1
2018-07-16 21:27:32.183: [ora.FRA.dg][3189217024]{0:0:967} [check] CrsCmd::ClscrsCmdData::stat entity 1 statflag 33 useFilter 0
2018-07-16 21:27:32.201: [ora.FRA.dg][3189217024]{0:0:967} [check] DgpAgent::runCheck: asm stat asmRet 0
2018-07-16 21:27:32.202: [ora.FRA.dg][3189217024]{0:0:967} [check] DgpAgent::getConnxn connected
2018-07-16 21:27:32.202: [ora.FRA.dg][3189217024]{0:0:967} [check] DgpAgent::queryDgStatus dgName FRA ret 0
2018-07-16 21:27:40.774: [ora.evmd][3189217024]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:27:40.774: [ora.evmd][3189217024]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:27:40.774: [ora.evmd][3189217024]{0:0:2} [check] Deep check returned 1
2018-07-16 21:27:42.116: [ora.LISTENER.lsnr][3189217024]{0:0:2} [check] Utils:execCmd action = 3 flags = 38 ohome = (null) cmdname = lsnrctl.
2018-07-16 21:27:42.219: [ora.LISTENER.lsnr][3189217024]{0:0:2} [check] execCmd ret = 0
2018-07-16 21:28:09.864: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115800
2018-07-16 21:28:10.776: [ora.evmd][3176802048]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:28:10.776: [ora.evmd][3176802048]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:28:10.776: [ora.evmd][3176802048]{0:0:2} [check] Deep check returned 1
2018-07-16 21:28:39.866: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115808
2018-07-16 21:28:40.778: [ora.evmd][3157808896]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:28:40.778: [ora.evmd][3157808896]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:28:40.778: [ora.evmd][3157808896]{0:0:2} [check] Deep check returned 1
2018-07-16 21:28:42.110: [ora.LISTENER.lsnr][3157808896]{0:0:2} [check] Utils:execCmd action = 3 flags = 38 ohome = (null) cmdname = lsnrctl.
2018-07-16 21:28:42.213: [ora.LISTENER.lsnr][3157808896]{0:0:2} [check] execCmd ret = 0
2018-07-16 21:29:09.868: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115816
2018-07-16 21:29:10.780: [ora.evmd][3159910144]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:29:10.780: [ora.evmd][3159910144]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:29:10.780: [ora.evmd][3159910144]{0:0:2} [check] Deep check returned 1
2018-07-16 21:29:39.869: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115824
2018-07-16 21:29:40.772: [ora.evmd][3189217024]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:29:40.772: [ora.evmd][3189217024]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:29:40.772: [ora.evmd][3189217024]{0:0:2} [check] Deep check returned 1
2018-07-16 21:29:42.114: [ora.LISTENER.lsnr][3189217024]{0:0:2} [check] Utils:execCmd action = 3 flags = 38 ohome = (null) cmdname = lsnrctl.
2018-07-16 21:29:42.217: [ora.LISTENER.lsnr][3189217024]{0:0:2} [check] execCmd ret = 0
2018-07-16 21:30:10.778: [ora.evmd][3176802048]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:30:10.778: [ora.evmd][3176802048]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:30:10.778: [ora.evmd][3176802048]{0:0:2} [check] Deep check returned 1
2018-07-16 21:30:39.863: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115838
2018-07-16 21:30:40.775: [ora.evmd][3176802048]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:30:40.775: [ora.evmd][3176802048]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:30:40.775: [ora.evmd][3176802048]{0:0:2} [check] Deep check returned 1
2018-07-16 21:30:42.118: [ora.LISTENER.lsnr][3176802048]{0:0:2} [check] Utils:execCmd action = 3 flags = 38 ohome = (null) cmdname = lsnrctl.
2018-07-16 21:30:42.221: [ora.LISTENER.lsnr][3176802048]{0:0:2} [check] execCmd ret = 0
2018-07-16 21:31:09.865: [ AGFW][3187115776]{0:0:2} Agent received the message: AGENT_HB[Engine] ID 12293:115846
2018-07-16 21:31:10.777: [ora.evmd][3157808896]{0:0:2} [check] clsdmc_respget return: status=0, ecode=1
2018-07-16 21:31:10.777: [ora.evmd][3157808896]{0:0:2} [check] DaemonAgent::check returned 0
2018-07-16 21:31:10.777: [ora.evmd][3157808896]{0:0:2} [check] Deep check returned 1
For ASM database startup issue in linux , we need to apply a patch for oracle database 11.2.0.4
Patch : 16870214
After applying this patch , Database is able to start . please note it
Related
I upgraded consul to 1.8.7 when I moved to Ubuntu 22. I am facing the following error,
● consul.service - Consul Agent
Loaded: loaded (/lib/systemd/system/consul.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-01-12 06:00:59 UTC; 22min ago Main PID: 206769 (consul)
Tasks: 20 (limit: 119416)
Memory: 19.8M
CPU: 3.686s
CGroup: /system.slice/consul.service
└─206769 /usr/bin/consul agent -config-dir /etc/consul
node231 consul[206769]: 2023-01-12T06:22:56.783Z [WARN] agent:
error getting server health from server: server=node231 error="rpc
error getting client: failed to get conn: dial tcp
10.142.0.39:0->10.142.0.39:8300: i/o timeout" node231 consul[206769]: 2023-01-12T06:22:56.783Z [WARN] agent: error getting server health
from server: server=node231 error="rpc error getting client: failed to
get conn: rpc error: lead thread didn't get connection" node231
consul[206769]: 2023-01-12T06:22:56.783Z [WARN] agent: error
getting server health from server: server=node231 error="rpc error
getting client: failed to get conn: rpc error: lead thread didn't get
connection" node231 consul[206769]: 2023-01-12T06:22:56.783Z
[WARN] agent: error getting server health from server: server=node231
error="rpc error getting client: failed to get conn: rpc error: lead
thread didn't get connection" node231 consul[206769]:
2023-01-12T06:22:56.783Z [WARN] agent: error getting server health
from server: server=node231 error="rpc error getting client: failed to
get conn: rpc error: lead thread didn't get connection" node231
consul[206769]: 2023-01-12T06:22:56.783Z [WARN] agent: error
getting server health from server: server=node231 error="rpc error
getting client: failed to get conn: rpc error: lead thread didn't get
connection" node231 consul[206769]: 2023-01-12T06:22:57.782Z
[WARN] agent: error getting server health from server: server=node231
error="context deadline exceeded" node231 consul[206769]:
2023-01-12T06:22:59.783Z [WARN] agent: error getting server health
from server: server=node231 error="context deadline exceeded" node231
consul[206769]: 2023-01-12T06:23:01.782Z [WARN] agent: error
getting server health from server: server=node231 error="context
deadline exceeded" node231 consul[206769]:
2023-01-12T06:23:03.160Z [ERROR] agent.http: Request error: method=GET
url=/v1/agent/check/fail/service:puppet from=127.0.0.1:55702
error="method GET not allowed"
My server info
agent:
check_monitors = 0
check_ttls = 2
checks = 2
services = 2
build:
prerelease =
revision =
version = 1.8.7
consul:
acl = disabled
bootstrap = true
known_datacenters = 1
leader = true
leader_addr = 10.142.0.39:8300
server = true
raft:
applied_index = 51
commit_index = 51
fsm_pending = 0
last_contact = 0
last_log_index = 51
last_log_term = 2
last_snapshot_index = 0
last_snapshot_term = 0
latest_configuration = [{Suffrage:Voter ID:c3b23645-fbf1-4a29-3497-d6cccb7d0941 Address:10.142.0.39:8300}]
latest_configuration_index = 0
num_peers = 0
protocol_version = 3
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Leader
term = 2
runtime:
arch = amd64
cpu_count = 32
goroutines = 77
max_procs = 32
os = linux
version = go1.17
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 1
event_time = 2
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 1
members = 1
query_queue = 0
query_time = 1
serf_wan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 1
members = 1
query_queue = 0
query_time = 1
Is there anything else I need to take care for new version of consul?
I am running an Oracle 12c application on 64-bit Windows 2016 VM. The application connects via TNS using a 32-bit Oracle ODBC connection. Intermittently but frequently I get ORA-03135 errors.
Having read many posts about this I have tried a lot of things i.e. Turning on/off connection pooling, setting SQLNET.EXPIRE_TIME, SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT etc. but nothing solves the issue.
I have managed to create a trace file that shows details of the error which appears to be a network issue. Can anyone out there tell me what it means and how I can resolve it?
2018-07-26 13:20:36.561 : nsdofls:sending NSPTDA packet
2018-07-26 13:20:36.561 : nspsend:entry
2018-07-26 13:20:36.561 : nspsend:plen=33, type=6
2018-07-26 13:20:36.561 : nttwr:entry
2018-07-26 13:20:36.561 : ntt2err:entry
2018-07-26 13:20:36.561 : ntt2err:soc 836 error - operation=6, ntresnt[0]=517, ntresnt[1]=54, ntresnt[2]=0
2018-07-26 13:20:36.561 : ntt2err:exit
2018-07-26 13:20:36.571 : nttwr:exit
2018-07-26 13:20:36.571 : nspsend:0 bytes to transport
2018-07-26 13:20:36.571 : nspsend:transport write error
2018-07-26 13:20:36.571 : nspsend:error exit
2018-07-26 13:20:36.579 : nserror:entry
2018-07-26 13:20:36.579 : nserror:nsres: id=0, op=67, ns=12547, ns2=12560; nt[0]=517, nt[1]=54, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
2018-07-26 13:20:36.579 : nsdofls:exit (-1)
2018-07-26 13:20:36.579 : nsdo:nsctxrnk=0
2018-07-26 13:20:36.579 : nsdo:error exit
2018-07-26 13:20:36.579 : nioqrc:send failed: bl = 1, nicbl = 0
2018-07-26 13:20:36.579 : nioqper: error from nioqrc
2018-07-26 13:20:36.579 : nioqper: ns main err code: 12547
2018-07-26 13:20:36.579 : nioqper: ns (2) err code: 12560
2018-07-26 13:20:36.579 : nioqper: nt main err code: 517
2018-07-26 13:20:36.579 : nioqper: nt (2) err code: 54
2018-07-26 13:20:36.579 : nioqper: nt OS err code: 0
2018-07-26 13:20:36.579 : nioqer:entry
2018-07-26 13:20:36.579 : nioqer: incoming err = 12150
2018-07-26 13:20:36.592 : nioqce:entry
2018-07-26 13:20:36.592 : nioqce:exit
2018-07-26 13:20:36.593 : nioqer: returning err = 3135
2018-07-26 13:20:36.593 : nioqer:exit
2018-07-26 13:20:36.593 : nioqrc: returning error: 3135
I have a stripped binary which crashes and I want to reverse it. I tried the 'info file' to get the EntryPoint and set a breakpoint there. However a segmentation fault happens on one of the child processes...
[New process 40472]
process 40472 is executing new program: /usr/bin/dpkg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Inferior 2 (process 40472) exited normally]
E: Method http has died unexpectedly!
E: Sub-process http received a segmentation fault.
From the documentation I found the 'show inferior' but I cant find out how to see the specifics of the segfault ? I tried the 'set follow-fork-mode' to chile but it doesnt look like it is helping.
For example I would like to examine the values of the registers such as RIP etc.
Stracing the process produces this:
[pid 54137] writev(3, [{"\0\37", 2}, {"{\346\1\0\0\1\0\0\0\0\0\0\4http\4example\3org\0\0\1\0\1", 31}, {"\0\37", 2}, {"\357\24\1\0\0\1\0\0\0\0\0\0\4http\4example\3org\0\0\34\0\1", 31}], 4) = 66
[pid 54137] read(3, <unfinished ...>
[pid 54134] <... read resumed> "\10\376", 2) = 2
[pid 54134] read(3, "X\250AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"..., 2302) = 2302
[pid 54134] close(3) = 0
[pid 54134] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
[pid 54134] +++ killed by SIGSEGV +++
[pid 54131] <... select resumed> ) = 1 (in [5], left {0, 425835})
[pid 54131] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=54134, si_uid=0, si_status=SIGSEGV, si_utime=0, si_stime=1} ---
close(4)
....
....
....
close(5) = 0
close(4) = 0
write(2, "E", 1E) = 1
write(2, ": ", 2: ) = 2
write(2, "Method http has died unexpectedl"..., 34Method http has died unexpectedly!) = 34
write(2, "\n", 1
) = 1
write(2, "E", 1E) = 1
write(2, ": ", 2: ) = 2
write(2, "Sub-process http received a segm"..., 47Sub-process http received a segmentation fault.) = 47
write(2, "\n", 1
) = 1
close(3) = 0
exit_group(100) = ?
+++ exited with 100 +++
I tried to set up RStudio Server on a newly installed Ubuntu 14.04 64bit machine. I followed the instructions but when I browsed the portal, I was told with a popup that I wasn't able to connect to the service.
From traceback:
13737 socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
13737 connect(3, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = 0
13737 sendto(3, "<11>Oct 14 14:27:59 rsession-roo"..., 283, MSG_NOSIGNAL, NULL, 0) = 283
13737 exit_group(1) = ?
13737 +++ exited with 1 +++
13708 <... rt_sigtimedwait resumed> ) = 17
13708 wait4(13737, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], WNOHANG, NULL) = 13737
13708 rt_sigtimedwait([INT QUIT TERM CHLD], NULL, NULL, 8 <unfinished ...>
13729 connect(9, {sa_family=AF_LOCAL, sun_path="/tmp/rstudio-rsession/root"}, 28) = -1 ECONNREFUSED (Connection refused)
13728 connect(9, {sa_family=AF_LOCAL, sun_path="/tmp/rstudio-rsession/root"}, 28) = -1 ECONNREFUSED (Connection refused)
From /var/log/syslog:
Oct 14 14:26:42 iZ28xtxldicZ rsession-root[13730]: ERROR system error 13 (Permission denied); OCCURRED AT: int main(int, char* const*) /home/ubuntu/rstudio/src/cpp/session/SessionMain.cpp:3003; LOGGED FROM: int main(int, char* const*) /home/ubuntu/rstudio/src/cpp/session/SessionMain.cpp:3004
Oct 14 14:26:52 iZ28xtxldicZ rserver[13708]: ERROR system error 111 (Connection refused) [request-uri=/rpc/client_init]; OCCURRED AT: void rstudio::core::http::LocalStreamAsyncClient::handleConnect(const boost::system::error_code&) /home/ubuntu/rstudio/src/cpp/core/include/core/http/LocalStreamAsyncClient.hpp:84; LOGGED FROM: void rstudio::server::session_proxy::{anonymous}::logIfNotConnectionTerminated(const rstudio::core::Error&, const rstudio::core::http::Request&) /home/ubuntu/rstudio/src/cpp/server/ServerSessionProxy.cpp:269
Anyone knows what's happening here?
PS: At first it was telling ENOENT over a path to the temp folder, and now it's telling something different after I created it manually.
I installed DB2 10.1 FP4 on Windows server 2012 R2 successfully.
When I try to start database using db2start I am getting below error.
DB2 : The service has returned a service-specific error code.
SQL1042C An unexpected system error occurred. SQLSTATE=58004
db2diag.log has below error.
2015-05-14-16.34.51.630000+540 I95881F1126 LEVEL: Error
PID : 4728 TID : 4996 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
HOSTNAME: <Machine name>
EDUID : 4996 EDUNAME: db2sysc
FUNCTION: DB2 Common, Cryptography, cryptDynamicLoadGSKitCrypto, probe:998
MESSAGE : ECF=0x90000076=-1879048074=ECF_LIB_CANNOT_LOAD
Cannot load the specified library
DATA #1 : unsigned integer, 4 bytes
70
DATA #2 : String, 48 bytes
D:\PROGRA~1\IBM\SQLLIB\bin\icc64\gsk8iccs_64.dll
CALLSTCK:
[0] 0x00007FF93D9642A4 pdOSSeLoggingCallback + 0x134
[1] 0x00007FF93EF1033E ossLog + 0x15E
[2] 0x00007FF93EF1023B ossLog + 0x5B
[3] 0x00007FF91D8E75ED cryptDynamicLoadGSKitCrypto + 0x65D
[4] 0x00007FF91D8E6724 cryptContextRealInit + 0x144
[5] 0x00007FF91D8E6337 cryptContextInit + 0x117
[6] 0x00007FF91C9002E5 sqloRunInstance + 0x1C5
[7] 0x00007FF691442700 0x00007FF691442700 + 0x0
[8] 0x00007FF691441974 0x00007FF691441974 + 0x0
[9] 0x00007FF946B516AD BaseThreadInitThunk + 0xD
[10] 0x00007FF946D04629 RtlUserThreadStart + 0x1D
2015-05-14-16.34.51.834000+540 I97009F922 LEVEL: Error
PID : 4728 TID : 4996 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
HOSTNAME: <Machine name>
EDUID : 4996 EDUNAME: db2sysc
FUNCTION: DB2 Common, Cryptography, cryptContextInit, probe:105
MESSAGE : ECF=0x90000076=-1879048074=ECF_LIB_CANNOT_LOAD
Cannot load the specified library
DATA #1 : Hex integer, 4 bytes
0x90000076
CALLSTCK:
[0] 0x00007FF93D9642A4 pdOSSeLoggingCallback + 0x134
[1] 0x00007FF93EF1033E ossLog + 0x15E
[2] 0x00007FF93EF1023B ossLog + 0x5B
[3] 0x00007FF91D8E63D5 cryptContextInit + 0x1B5
[4] 0x00007FF91C9002E5 sqloRunInstance + 0x1C5
[5] 0x00007FF691442700 0x00007FF691442700 + 0x0
[6] 0x00007FF691441974 0x00007FF691441974 + 0x0
[7] 0x00007FF946B516AD BaseThreadInitThunk + 0xD
[8] 0x00007FF946D04629 RtlUserThreadStart + 0x1D
2015-05-14-16.34.51.834000+540 I97933F426 LEVEL: Severe
PID : 4728 TID : 4996 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
HOSTNAME: <Machine name>
EDUID : 4996 EDUNAME: db2sysc
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:50
MESSAGE : ECF=0x90000076=-1879048074=ECF_LIB_CANNOT_LOAD
Cannot load the specified library
2015-05-14-16.34.51.834000+540 I98361F529 LEVEL: Severe
PID : 4728 TID : 4996 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
HOSTNAME: <Machine name>
EDUID : 4996 EDUNAME: db2sysc
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:2263
MESSAGE : SQL1042C An unexpected system error occurred.
Any help is appreciate.