Community

Subscribe
Highlighted
Accepted Solution

Profile creation failed but there is any error

Hello all ,

I've tried to create a new profile . After process is finished , I got the message 'Profile creation failed'  in the 'Result ' field . Then I clicked on 'Operation Details' , all what I can see there is blank and nothing there.

OS : WIndows Server 2008 R2 64 bits

SMO for Oracle : 3.1

Database : Oracle 11.2.0.3

Snapdrive : 6.4

I  attach the screenshot in this discussion . It's very hard for me to troubleshoot the problem without error .  Please help me !

Thanks and Regards

Tien

Re: Profile creation failed but there is any error

Hello Tien,

Can you please send the smo log which would help to debug this further.

Regards,

Himanshu

Re: Profile creation failed but there is any error

Hi Himanshu,

Here below is logfile when I create the profile .

STATUS | wrapper  | 2013/01/07 12:35:13 | --> Wrapper Started as Service

STATUS | wrapper  | 2013/01/07 12:35:13 | Java Service Wrapper Standard Edition 3.3.1

STATUS | wrapper  | 2013/01/07 12:35:13 |   Copyright (C) 1999-2008 Tanuki Software, Inc.  All Rights Reserved.

STATUS | wrapper  | 2013/01/07 12:35:13 |     http://wrapper.tanukisoftware.org

STATUS | wrapper  | 2013/01/07 12:35:13 |   Licensed to Network Appliance, Inc. for SnapManager

STATUS | wrapper  | 2013/01/07 12:35:13 |

STATUS | wrapper  | 2013/01/07 12:35:13 | Launching a JVM...

ERROR  | wrapper  | 2013/01/07 12:35:45 | Startup failed: Timed out waiting for a signal from the JVM.

ADVICE | wrapper  | 2013/01/07 12:35:45 |

ADVICE | wrapper  | 2013/01/07 12:35:45 | ------------------------------------------------------------------------

ADVICE | wrapper  | 2013/01/07 12:35:45 | Advice:

ADVICE | wrapper  | 2013/01/07 12:35:45 | The Wrapper consists of a native component as well as a set of classes

ADVICE | wrapper  | 2013/01/07 12:35:45 | which run within the JVM that it launches.  The Java component of the

ADVICE | wrapper  | 2013/01/07 12:35:45 | Wrapper must be initialized promptly after the JVM is launched or the

ADVICE | wrapper  | 2013/01/07 12:35:45 | Wrapper will timeout, as just happened.  Most likely the main class

ADVICE | wrapper  | 2013/01/07 12:35:45 | specified in the Wrapper configuration file is not correctly initializing

ADVICE | wrapper  | 2013/01/07 12:35:45 | the Wrapper classes:

ADVICE | wrapper  | 2013/01/07 12:35:45 |     com.netapp.dlm.server.WindowsServiceWrapper

ADVICE | wrapper  | 2013/01/07 12:35:45 | While it is possible to do so manually, the Wrapper ships with helper

ADVICE | wrapper  | 2013/01/07 12:35:45 | classes to make this initialization processes automatic.

ADVICE | wrapper  | 2013/01/07 12:35:45 | Please review the integration section of the Wrapper's documentation

ADVICE | wrapper  | 2013/01/07 12:35:45 | for the various methods which can be employed to launch an application

ADVICE | wrapper  | 2013/01/07 12:35:45 | within the Wrapper:

ADVICE | wrapper  | 2013/01/07 12:35:45 |     http://wrapper.tanukisoftware.org/doc/english/integrate.html

ADVICE | wrapper  | 2013/01/07 12:35:45 | ------------------------------------------------------------------------

ADVICE | wrapper  | 2013/01/07 12:35:45 |

ERROR  | wrapper  | 2013/01/07 12:35:45 | JVM did not exit on request, terminated

STATUS | wrapper  | 2013/01/07 12:35:52 | Launching a JVM...

ERROR  | wrapper  | 2013/01/07 12:36:24 | Startup failed: Timed out waiting for a signal from the JVM.

ADVICE | wrapper  | 2013/01/07 12:36:24 |

ADVICE | wrapper  | 2013/01/07 12:36:24 | ------------------------------------------------------------------------

ADVICE | wrapper  | 2013/01/07 12:36:24 | Advice:

ADVICE | wrapper  | 2013/01/07 12:36:24 | The Wrapper consists of a native component as well as a set of classes

ADVICE | wrapper  | 2013/01/07 12:36:24 | which run within the JVM that it launches.  The Java component of the

ADVICE | wrapper  | 2013/01/07 12:36:24 | Wrapper must be initialized promptly after the JVM is launched or the

ADVICE | wrapper  | 2013/01/07 12:36:24 | Wrapper will timeout, as just happened.  Most likely the main class

ADVICE | wrapper  | 2013/01/07 12:36:24 | specified in the Wrapper configuration file is not correctly initializing

ADVICE | wrapper  | 2013/01/07 12:36:24 | the Wrapper classes:

ADVICE | wrapper  | 2013/01/07 12:36:24 |     com.netapp.dlm.server.WindowsServiceWrapper

ADVICE | wrapper  | 2013/01/07 12:36:24 | While it is possible to do so manually, the Wrapper ships with helper

ADVICE | wrapper  | 2013/01/07 12:36:24 | classes to make this initialization processes automatic.

ADVICE | wrapper  | 2013/01/07 12:36:24 | Please review the integration section of the Wrapper's documentation

ADVICE | wrapper  | 2013/01/07 12:36:24 | for the various methods which can be employed to launch an application

ADVICE | wrapper  | 2013/01/07 12:36:24 | within the Wrapper:

ADVICE | wrapper  | 2013/01/07 12:36:24 |     http://wrapper.tanukisoftware.org/doc/english/integrate.html

ADVICE | wrapper  | 2013/01/07 12:36:24 | ------------------------------------------------------------------------

ADVICE | wrapper  | 2013/01/07 12:36:24 |

ERROR  | wrapper  | 2013/01/07 12:36:24 | JVM did not exit on request, terminated

STATUS | wrapper  | 2013/01/07 12:36:29 | Launching a JVM...

INFO   | jvm 3    | 2013/01/07 12:36:31 | WrapperManager: Initializing...

ERROR  | wrapper  | 2013/01/07 12:37:06 | Startup failed: Timed out waiting for signal from JVM.

ERROR  | wrapper  | 2013/01/07 12:37:06 | JVM did not exit on request, terminated

STATUS | wrapper  | 2013/01/07 12:37:11 | Launching a JVM...

INFO   | jvm 4    | 2013/01/07 12:37:15 | WrapperManager: Initializing...

INFO   | wrapper  | 2013/01/07 12:37:30 | Wrapper Process has not received any CPU time for 13 seconds.  Extending timeouts.

ERROR  | wrapper  | 2013/01/07 12:38:07 | Startup failed: Timed out waiting for signal from JVM.

ERROR  | wrapper  | 2013/01/07 12:38:07 | JVM did not exit on request, terminated

STATUS | wrapper  | 2013/01/07 12:38:12 | Launching a JVM...

INFO   | jvm 5    | 2013/01/07 12:38:13 | WrapperManager: Initializing...

INFO   | jvm 5    | 2013/01/07 12:38:39 | [ WARN] SMO-01091: Unsupported Operating System: windows version 6.1 on x64

INFO   | jvm 5    | 2013/01/07 12:38:39 | [ INFO] SMO-17100: SnapManager Server started on secure port 27216 with PID 3640.

INFO   | jvm 5    | 2013/01/07 12:38:39 | [ INFO] SMO-17111: SnapManager Server started on: https://Stobup03:27216/smo_v9/services/SMO

INFO   | jvm 5    | 2013/01/07 12:38:39 | [ INFO] SMO-17101: SnapManager Server internal RMI registry started on port 27217.

INFO   | jvm 5    | 2013/01/07 12:39:01 | [ INFO] SMO-17105: Shutdown of SnapManager Server initiated...

INFO   | jvm 5    | 2013/01/07 12:39:01 | [ INFO] SMO-17106: Shutdown of SnapManager Server completed.

STATUS | wrapper  | 2013/01/07 12:39:02 | <-- Wrapper Stopped

Thanks and Regards

Tien

Re: Profile creation failed but there is any error

Hi all,

The problem was due to user connecting to database is missing the ORA-DBA permission, The problem has been solved. !

Regards

Tien