ServerSocketChannel.bind () error in Oracl embedded JVM

Hello. I am researching Oracle for training purposes. I am currently trying to program in the embedded JVM.
And I found the following error:
if you use “ServerSocketChannel.bind (new InetSocketAddress (InetAddress.getLocalHost (). getHostAddress (), port)”,
then an error is caused:

**”java.net.SocketException: bind failed, errno = 10049
required address for its context is incorrect.
at sun.nio.ch.Net.bind0 (Native Method)
at sun.nio.ch.Net.bind (Net.java)
at sun.nio.ch.Net.bind (Net.java)
at sun.nio.ch.ServerSocketChannelImpl.bind (ServerSocketChannelImpl.java)
at java.nio.channels.ServerSocketChannel.bind (ServerSocketChannel.java)”**

Any attempt to bind ServerSocketChannel by name or IP address results in this error.
I have not found any description of this error on the Internet, and it is suggested that this
development error.
OS Windows7 64 bit, Windows 10. Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 – Production
Version 18.3.0.0.0
Partially this error corrects: “System.setProperty (“java.net.preferIPv4Stack”, “true”)”;
In this case, ServerSocketChannel.bind () works well,
but attempt to return ip address:
“ServerSocketChannel.socket (). GetInetAddress (). GetHostAddress ());”
or
“ServerSocketChannel.getLocalAddress ();”
causes an error

“java.lang.NullPointerException
at java.net.Inet4Address.getAddress(Inet4Address.java)
at java.net.Inet4Address.getHostAddress(Inet4Address.java)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java)”

therefore, this error is always called as soon as it tries to connect to the listener.
is it possible to fix it?

If this is a bug, what are the chances that Oracle will fix it?
Is it possible to send a request to the support service to eliminate this bug, if I do not have a license key?. Thank.

Related:

  • No Related Posts

VxRail: After cancelling failed attempt of upgrading to 4.5.210, following attempt fails with error “result returns more than one elements”

Article Number: 520991 Article Version: 6 Article Type: Break Fix



VxRail Appliance Family,VxRail Appliance Series,VxRail Software

If an attempt to upgrade to VxRail 4.5.210 software release failed and was canceled, following attempts can fail:

In WebGUI:

The error message: result returns more than one elements; nested exception is javax.persistence.NonUniqueResultException: result returns more than one elements. 

In lcm.log:

...with exception:org.springframework.dao.IncorrectResultSizeDataAccessException: result returns more than one elements; nested exception is javax.persistence.NonUniqueResultException: result returns more than one elements

During the upgrade, some network related tables can be populated twice incorrectly if there is a second attempt.

  • Take a snapshot of VxRail Manager.
  • Opens an SR requesting for resolution, and mention this KB in SR.

Related:

Error “XDDS:9984398A” on mandatory Site upgrade

Mandatory Site upgrade on first DDC fails with error “XDDS:9984398A”.

Exception:

Citrix.Console.Common.CitrixAggregateException One or more parallel operations failed

at Citrix.Console.Common.CitrixParallel.InternalForEach[TIn](IEnumerable`1 items, Action`1 operation, Int32 maxSimultaneous)

at Citrix.Console.PowerShellSdk.SiteInformationService.SiteInformationService.Refresh()

at Citrix.Console.DeliveryCenter.UI.ViewModel.DesktopStudioViewModel.LoadSiteState(IProgressReporter progressReporter)

at Citrix.Console.Common.OperationTimer.TimeBlock(Action operation)

at Citrix.Console.CommonControls.ProgressDisplay.GenericProgressOperationWithFeedBack.PerformOperationInternal()

at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowOperation.PerformOperation()

at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowViewModel.PerformAction(Action operationComplete)


Inner Exception:

Citrix.Console.Models.Exceptions.ScriptException An unexpected error occurred.

at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.CreateException[T](ICommonLog logger, ExecutionResults`1 results, ICmdletExecutionHost host)

at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.Execute[T](ISdkCmdlet`1 sdkCmd, ICmdletExecutionHost host, Boolean allowFailover)

at Citrix.Console.PowerShellSdk.LicensingService.Scripts.GetLicenseInformationScript.RunScript()

at Citrix.Console.PowerShellInteraction.PowerShellScript`1.Run()

at Citrix.Console.PowerShellSdk.SiteInformationService.SiteInformationService.GetLicenseAlert()

at Citrix.Console.PowerShellSdk.SiteInformationService.SiteInformationService.<>c__DisplayClass33_0.<Refresh>b__7()

at Citrix.Console.Common.CitrixParallel.<>c__DisplayClass4_1`1.<InternalForEach>b__0(Object arg)

Related:

What are others doing for User Profile Exclusions

I need a solution

We need an exclusion for an application folder that resides under the logged on users profile.  C:Users<username>AppData….

This is a requirement from the application release notes.  It seems that SEP only has the USER_PROFILE variable available which by their definition is “File system folders that correspond to all the users.  So this would be c:documents and SettingsAll Users for win7 and C:programdata for win 10.

I am wondering what others are doing for exceptions required by an application that SEP does not support with an available variable?  Is there a way to script the exception after the user has logged in for the first time?

Thanks.

0

Related:

ReocverPoint for VM: Deployment fails when trying to discover the available vRPAs

Article Number: 502082 Article Version: 4 Article Type: Break Fix



RecoverPoint,RecoverPoint for Virtual Machines

Deployment fails when trying to get the available vRPAs, not able to continue the installation. This normally happens in a large scaled RP4VM environment.


Symptoms found in the logs:

Caused by: com.emc.recoverpoint.cluster_logic.inner_model.exception.RpaAdapterException: Exception caught in server [ java.lang.OutOfMemoryError ]

at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.calls.BaseRpaCall.logAndThrow(BaseRpaCall.java:51)

at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.calls.BaseRpaCall.call(BaseRpaCall.java:37)

at com.emc.recoverpoint.cluster_logic.cl_rpa_adapter_core.RpaAdapterImpl.getAvailableVrpas(RpaAdapterImpl.java:53)

at com.emc.recoverpoint.deployment.task.GetAvailableVrpasTask.perform(GetAvailableVrpasTask.java:54)

… 9 more

Affected versions: 5.0.X

Scanning all ESX clusters for vRPAs then filtering, instead of fetching under relevant ESX cluster to begin with which caused ClusterLogic fails on OutOfMemory.

Workaround:

Deploy using restricted user that is limited to the ESX cluster that the RPAs are running from.

Resolution:

5.1

Related:

  • No Related Posts

Problem with Policy Exceptions

I need a solution

I’ve a problem with a Policy Exceptions.

Example:
I created a Policy that search for the keywords: aaa, bbb, ccc. I have a textfile with aaa, bbb, ccc. If I scan with this policy I got an Incident with 3 matches.

I enlarged the policy with with an exception for the keyword ccc. If I scan the textfile I didn’t get an Incident. It seems that my scan scanned for the exception first and if this matched the scan skipped the file.

I’m looking for a solution that scan the whole file, count all matches minus the “exception matches”. How can I achieve this?

0

Related:

  • No Related Posts

StoreFront 3.5 upgrade to 3.15 fails with error ” Citrix StoreFront 3.15.0.18019 failed”

StoreFront Version 3.5 fails to upgrade to version 3.15, during the upgrade process the wizard displays the following message “Citrix StoreFront 3.15.0.18019 failed”

At the bottom of the upgrade wizard window, another message is displayed “NOTE: An error occurred during installation. Please ensure all the required prerequisites have been installed and run the installer again”

StorefrontError

The install logs in c:WindowsTempStoreFront eg. Citrix-DeliveryServicesSetupConsole-yyyy-mm-dd hh-mm-ss.log, show the following error:

Begin SnapshotConfiguration

Creating version snapshot for version ‘3.5.0.23’.

Loading backup history configuration

An error occurred creating the snapshot: ‘System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for citrix.deliveryservices/sessionManager: Could not load file or assembly ‘Citrix.DeliveryServices.Security.CitrixAuth.Configuration, Version=3.14.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856’ or one of its dependencies. The system cannot find the file specified. (C:inetpubwwwrootCitrixStoreweb.config line 48) —> System.IO.FileNotFoundException: Could not load file or assembly ‘Citrix.DeliveryServices.Security.CitrixAuth.Configuration, Version=3.14.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856’ or one of its dependencies. The system cannot find the file specified.

at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)

at System.Configuration.MgmtConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)

at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

— End of inner exception stack trace —

at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)

at System.Configuration.ConfigurationSectionCollection.Get(String name)

at System.Configuration.ConfigurationSectionCollection.<GetEnumerator>d__0.MoveNext()

at Citrix.DeliveryServices.InstallController.Configuration.ConfigFileValidator.ReadSectionGroup(Configuration config, ConfigurationSectionGroup sectionGroup)

at Citrix.DeliveryServices.InstallController.Configuration.ConfigFileValidator.Validate()

at Citrix.DeliveryServices.InstallController.Configuration.VersionData.BackupConfigFile(IFeatureInstance instance, DirectoryInfo instanceBackup)

at Citrix.DeliveryServices.InstallController.Configuration.VersionData.BackupFeatureInstances()

at Citrix.DeliveryServices.InstallController.Configuration.VersionData.Create(Version version, String backupPath)

at Citrix.DeliveryServices.InstallController.ConfigurationController.CreateVersionSnapshot(Version version)’.

Exception thrown by custom action:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for citrix.deliveryservices/sessionManager: Could not load file or assembly ‘Citrix.DeliveryServices.Security.CitrixAuth.Configuration, Version=3.14.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856’ or one of its dependencies. The system cannot find the file specified. (C:inetpubwwwrootCitrixStoreweb.config line 48) —> System.IO.FileNotFoundException: Could not load file or assembly ‘Citrix.DeliveryServices.Security.CitrixAuth.Configuration, Version=3.14.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856’ or one of its dependencies. The system cannot find the file specified.

at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)

at System.Configuration.MgmtConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)

at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

— End of inner exception stack trace —

Related:

DLP 15.x – Unable to logon Enforce after reboot/refresh server

I need a solution

Hi,

We were trying to reboot the server recently due to slow incident detection, however when trying to logon to Enforce it keep looping.

ProtectManager/GlobalDialog?type=NOT_FOUND

Error from tomcat:

Exception sending context initialized event to listener instance of class com.vontu.manager.spring.ManagerContextLoaderListener
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘managerSpringConfiguration’: Unsatisfied dependency expressed through field ‘systemKeyStore’: Error creating bean with name ‘getKeyIgnition’: Invocation of init method failed; nested exception is org.springframework.dao.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS
; SQL [n/a]; nested exception is org.hibernate.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS
; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘getKeyIgnition’: Invocation of init method failed; nested exception is org.springframework.dao.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS
; SQL [n/a]; nested exception is org.hibernate.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS

    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:569)
    at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88)
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:349)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1214)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:543)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:776)
    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:861)
    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:541)
    at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:444)
    at com.vontu.manager.spring.ManagerContextLoaderListener.configureAndRefreshWebApplicationContext(ManagerContextLoaderListener.java:43)
    at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:326)
    at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5118)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5634)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899)
    at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:133)
    at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:156)
    at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:145)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:873)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1260)
    at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2002)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:748)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘getKeyIgnition’: Invocation of init method failed; nested exception is org.springframework.dao.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS
; SQL [n/a]; nested exception is org.hibernate.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS

    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:136)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
    at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:207)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1214)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1054)
    at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1019)
    at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:566)
    … 33 more
Caused by: org.springframework.dao.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS
; SQL [n/a]; nested exception is org.hibernate.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS

    at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:265)
    at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:244)
    at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:521)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
    at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:483)
    at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:290)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
    at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
    at com.vontu.enforce.domainlayer.events.system.SystemEventLogger$$EnhancerBySpringCGLIB$$f967d9fd.logEvent(<generated>)
    at com.vontu.config.manager.crypto.ManagerKeyIgnitionHandler.onKeysIgnited(ManagerKeyIgnitionHandler.java:55)
    at com.vontu.enforce.domainlayer.crypto.impl.KeyIgnitionFactoryBean.performKeyIgnition(KeyIgnitionFactoryBean.java:93)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:365)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:310)
    at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:133)
    … 46 more
Caused by: org.hibernate.QueryTimeoutException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS

    at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:151)
    at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49)
    at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
    at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110)
    at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:129)
    at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:81)
    at com.sun.proxy.$Proxy142.executeBatch(Unknown Source)
    at org.hibernate.engine.jdbc.batch.internal.BatchingBatch.performExecution(BatchingBatch.java:110)
    at org.hibernate.engine.jdbc.batch.internal.BatchingBatch.doExecuteBatch(BatchingBatch.java:101)
    at org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl.execute(AbstractBatchImpl.java:161)
    at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.executeBatch(JdbcCoordinatorImpl.java:162)
    at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:357)
    at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:275)
    at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:326)
    at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:52)
    at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1214)
    at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:403)
    at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.beforeTransactionCommit(JdbcTransaction.java:101)
    at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:175)
    at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:75)
    at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:517)
    … 63 more
Caused by: java.sql.BatchUpdateException: ORA-01654: unable to extend index PROTECT.SYSTEMEVENT_FB4A by 128 in tablespace USERS

    at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:12296)
    at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:246)
    at com.vontu.util.jdbc.LoggingStatement.executeBatch(LoggingStatement.java:212)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:122)
    … 79 more

0

Related:

Description for individual Exceptions

I need a solution

Good afternoon,

    Just looking to see if this is even an option or someything I can move to a good idea. Currently in our SEPM we have many exception groups that are created depending on individual application that the vendor requires them. From one standpoint it is convenient to have each group named by the application however, that means it is a pain to manage. So I am changing our groups to basically a standard SEP group, a group for exceptions, test group…..

    I would like to be able to annotate what application each exception is for for tracking and audit purposes. However, I do not see a descriptionspace available when I create the individual exceptions. Has any had a better way of doing this?

Currently on SEP 14.2.770 on Server 2016. Environment uses mix of OS

0

Related:

ViPR 3.0 SP1: Unable to Discover Unity Array in ViPR Controller

Article Number: 487616 Article Version: 3 Article Type: Break Fix



ViPR Controller Controller 3.0

When Attempting to discover Array Model Unity 600F. Discovery fails and errors can be noted from the ViPR controllersvc.logs:

Errors from Controllersvc.logs:

Vipr# vipr# controllersvc 2016-08-03 12:19:18,699 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO KHRequests.java (line 158) got data: {“@base”:”https://XXX.XXX.XXX.XXX/api/types/system/instances?fields=serialNumber,name,model,id&per_page=2000″,”updated”:”2016-08-03T12:19:18.702Z”,”links”:[{“rel”:”self”,”href”:”&page=1″}],”entries”:[{“@base”:”https://XXX.XXX.XXX.XXX/api/instances/system”,”updated”:”2016-08-03T12:19:18.702Z”,”links”:[{“rel”:”self”,”href”:”/0″}],”content”:{“id”:”0″,”name”:”XXXXXXXXX-APM00XXXXXXXXX“,”model”:”Unity 600F”,”serialNumber”:”APM00XXXXXXXXX”}}]}

vipr# vipr# controllersvc 2016-08-03 12:19:18,711 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO KHRequests.java (line 149) getting data: /api/types/fastVP/instances

vipr# vipr# controllersvc 2016-08-03 12:19:18,711 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO KHRequests.java (line 399) getting data: /api/types/fastVP/instances

vipr# vipr# controllersvc 2016-08-03 12:19:18,711 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO KHRequests.java (line 608) Setting fields:null

vipr# vipr# controllersvc 2016-08-03 12:19:18,830 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO KHRequests.java (line 406) 422:Client response status: 422

vipr# vipr# controllersvc 2016-08-03 12:19:18,830 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] ERROR KHRequests.java (line 657) GET request to:/api/types/fastVP/instances failed with status code: 422 message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

vipr# vipr# controllersvc 2016-08-03 12:19:18,830 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] ERROR VNXUnityCommunicationInterface.java (line 410) Discovery failed for VNX Unity urn:storageos:StorageSystem:2dbe60a4-9e3b-4550-abcf-1157936a1f56:vdc1: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

com.emc.storageos.vnxe.VNXeException: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

at com.emc.storageos.vnxe.requests.KHRequests.checkResponse(KHRequests.java:659)

at com.emc.storageos.vnxe.requests.KHRequests.sendGetRequest(KHRequests.java:444)

at com.emc.storageos.vnxe.requests.KHRequests.getDataForObjects(KHRequests.java:150)

at com.emc.storageos.vnxe.requests.FastVPRequest.get(FastVPRequest.java:22)

at com.emc.storageos.vnxe.VNXeApiClient.isFASTVPEnabled(VNXeApiClient.java:1869)

at com.emc.storageos.volumecontroller.impl.plugins.VNXUnityCommunicationInterface.discover(VNXUnityCommunicationInterface.java:245)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.invoke(DataCollectionJobInvoker.java:170)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.process(DataCollectionJobInvoker.java:120)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.invokeJob(DataCollectionJobConsumer.java:139)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.consumeItem(DataCollectionJobConsumer.java:86)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.consumeItem(DataCollectionJobConsumer.java:54)

at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:80)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

vipr# vipr# controllersvc 2016-08-03 12:19:18,832 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO AbstractApplicationContext.java (line 1020) Closing org.springframework.context.support.ClassPathXmlApplicationContext@9989e1c: startup date [Wed Aug 03 12:19:18 UTC 2016]; parent: org.springframework.context.support.FileSystemXmlApplicationContext@6fb554cc

vipr# vipr# controllersvc 2016-08-03 12:19:18,832 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO DefaultSingletonBeanRegistry.java (line 433) Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@10ca1376: defining beans [clientFactory,unityUnManagedObjectDiscoverer,partitionManager,unity]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory@4681c175

vipr# vipr# controllersvc 2016-08-03 12:19:18,833 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] ERROR DataCollectionJobConsumer.java (line 90) Discovery job failed for urn:storageos:StorageSystem:2dbe60a4-9e3b-4550-abcf-1157936a1f56:vdc1—>

com.emc.storageos.vnxe.VNXeException: error when discover VNXe: Discovery error, because the exception: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

at com.emc.storageos.volumecontroller.impl.plugins.VNXUnityCommunicationInterface.discover(VNXUnityCommunicationInterface.java:411)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.invoke(DataCollectionJobInvoker.java:170)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.process(DataCollectionJobInvoker.java:120)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.invokeJob(DataCollectionJobConsumer.java:139)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.consumeItem(DataCollectionJobConsumer.java:86)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.consumeItem(DataCollectionJobConsumer.java:54)

at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:80)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: com.emc.storageos.vnxe.VNXeException: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

at com.emc.storageos.vnxe.requests.KHRequests.checkResponse(KHRequests.java:659)

at com.emc.storageos.vnxe.requests.KHRequests.sendGetRequest(KHRequests.java:444)

at com.emc.storageos.vnxe.requests.KHRequests.getDataForObjects(KHRequests.java:150)

at com.emc.storageos.vnxe.requests.FastVPRequest.get(FastVPRequest.java:22)

at com.emc.storageos.vnxe.VNXeApiClient.isFASTVPEnabled(VNXeApiClient.java:1869)

at com.emc.storageos.volumecontroller.impl.plugins.VNXUnityCommunicationInterface.discover(VNXUnityCommunicationInterface.java:245)

… 9 more

vipr# vipr# controllersvc 2016-08-03 12:19:18,839 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO Operation.java (line 129) Setting operation to error due to an exception com.emc.storageos.vnxe.VNXeException: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}-error when discover VNXe: Discovery error, because the exception: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

vipr# vipr# controllersvc 2016-08-03 12:19:18,839 [916|unity|Discovery|XXX.XXX.XXX.XXX|3f98eaf0-7368-4485-bdc4-a4e9a3ebcac1] INFO Operation.java (line 131) Caused by: {}

com.emc.storageos.vnxe.VNXeException: error when discover VNXe: Discovery error, because the exception: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

at com.emc.storageos.volumecontroller.impl.plugins.VNXUnityCommunicationInterface.discover(VNXUnityCommunicationInterface.java:411)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.invoke(DataCollectionJobInvoker.java:170)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobInvoker.process(DataCollectionJobInvoker.java:120)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.invokeJob(DataCollectionJobConsumer.java:139)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.consumeItem(DataCollectionJobConsumer.java:86)

at com.emc.storageos.volumecontroller.impl.plugins.discovery.smis.DataCollectionJobConsumer.consumeItem(DataCollectionJobConsumer.java:54)

at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:80)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: com.emc.storageos.vnxe.VNXeException: The POST /api/types/fastVP/instances failed with the status code: 422 and the message: {“error”:{“errorCode”:131150138,”httpStatusCode”:422,”messages”:[{“en-US”:”Requested element, property or action is not supported by current platform:[fastVP]. (Error Code:0x7d1313a)”}],”created”:”2016-08-03T12:19:18.832Z”}}

at com.emc.storageos.vnxe.requests.KHRequests.checkResponse(KHRequests.java:659)

at com.emc.storageos.vnxe.requests.KHRequests.sendGetRequest(KHRequests.java:444)

at com.emc.storageos.vnxe.requests.KHRequests.getDataForObjects(KHRequests.java:150)

at com.emc.storageos.vnxe.requests.FastVPRequest.get(FastVPRequest.java:22)

at com.emc.storageos.vnxe.VNXeApiClient.isFASTVPEnabled(VNXeApiClient.java:1869)

at com.emc.storageos.volumecontroller.impl.plugins.VNXUnityCommunicationInterface.discover(VNXUnityCommunicationInterface.java:245)

… 9 more

Unity Array Support added to ViPR Controller at Version of ViPR 3.0 SP1.

The current supported version of the Unity Array the 300F Models.

Unity Array Models 400, 400F, 500, 500F, 600, 600F are currently not supported for Discovery in ViPR Controller 3.0 SP1.

The support of the Unity Array Models up to the 600F Models will be available in the 3.5 Release of ViPR Controller.

Notes:

EMC ViPR Controller 3.0.0.1 New Features

Key new and/or enhanced features in ViPR Controller 3.0.0.1 release include the following:

EMC Unity Support for Block:

• Discover Unity block and file

• Block volume creation/deletion

• Block volume creation/deletion in consistency group

• volume export/unexport

• Block snapshots – create/delete/restore snapshots

• Ingest Unity volumes

EMC Unity Support for File:

• Discover Unity as a separate storage system

• Create, Expand, Delete FileSystem operations

Related: