Categories and groups

[osjonathan]

I've just installed 2.6.1., and had it create a new (Oracle) table-structure. However I can't edit categories or groups. Both "group management" and "category management" result in a 500 error:

HTTP ERROR: 500 The data "The data "@8<5@ 3@C??K" is not legal for a JDOM character content: 0x1f is not a legal XML character." is not legal for a JDOM character content: 0x1f is not a legal XML character.

RequestURI=/geonetwork/srv/en/group.list Caused by: org.jdom.IllegalDataException: The data "The data "@8<5@ 3@C??K" is not legal for a JDOM character content: 0x1f is not a legal XML character." is not legal for a JDOM character content: 0x1f is not a legal XML character.

at org.jdom.Text.setText(Text.java:188) at org.jdom.Text.(Text.java:99) at org.jdom.Element.setText(Element.java:630) at jeeves.exceptions.JeevesException.toElement(JeevesException.java:82) at jeeves.server.dispatchers.ServiceManager.getError(ServiceManager.java:811) at jeeves.server.dispatchers.ServiceManager.handleError(ServiceManager.java:440) at jeeves.server.dispatchers.ServiceManager.dispatch(ServiceManager.java:429) at jeeves.server.JeevesEngine.dispatch(JeevesEngine.java:624) at jeeves.server.sources.http.JeevesServlet.execute(JeevesServlet.java:185) at jeeves.server.sources.http.JeevesServlet.doGet(JeevesServlet.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)

---

Also, no categories nor groups are appearing anywhere within geonetwork despite the defaults existing in the database. The Mckoi database works fine. I believe this has something to do with the cyrillic in the GROUPSDE and CATEGORIESDE tables. namely the .ru. Deleting the RU language rows from the database fixes the error.

[pmauduit]

Hello,

I had a similar problem in a different context ; it may be related of local Oracle configuration, and not a geonetwork issue ;

What is the current value of your NLS_LANG environment variable ? this should be coherent with your default database charset.

[osjonathan]

I haven't got a clue where to find that variable. Anyone know? Oracle was happy to show me the data in SQL Developer (as well as allow me to delete it).

[pmauduit]

Replying to osjonathan:

I haven't got a clue where to find that variable. Anyone know?

something like export | grep NLS_LANG or echo $NLS_LANG under Linux.

You can issue the following SQL query to check the current parameters of your DB :

SQL> select * from nls_database_parameters;

Hth,

[osjonathan]

Here's the output from that command.

"PARAMETER" "VALUE" "NLS_LANGUAGE" "AMERICAN" "NLS_TERRITORY" "AMERICA" "NLS_CURRENCY" "$" "NLS_ISO_CURRENCY" "AMERICA" "NLS_NUMERIC_CHARACTERS" ".," "NLS_CHARACTERSET" "WE8ISO8859P1" "NLS_CALENDAR" "GREGORIAN" "NLS_DATE_FORMAT" "DD-MON-RR" "NLS_DATE_LANGUAGE" "AMERICAN" "NLS_SORT" "BINARY" "NLS_TIME_FORMAT" "HH.MI.SSXFF AM" "NLS_TIMESTAMP_FORMAT" "DD-MON-RR HH.MI.SSXFF AM" "NLS_TIME_TZ_FORMAT" "HH.MI.SSXFF AM TZR" "NLS_TIMESTAMP_TZ_FORMAT" "DD-MON-RR HH.MI.SSXFF AM TZR" "NLS_DUAL_CURRENCY" "$" "NLS_COMP" "BINARY" "NLS_LENGTH_SEMANTICS" "BYTE" "NLS_NCHAR_CONV_EXCP" "FALSE" "NLS_NCHAR_CHARACTERSET" "AL16UTF16" "NLS_RDBMS_VERSION" "10.2.0.1.0"

[osjonathan]

That'll teach me for not using preview.

"PARAMETER"			"VALUE"
"NLS_LANGUAGE"			"AMERICAN"
"NLS_TERRITORY"			"AMERICA"
"NLS_CURRENCY"			"$"
"NLS_ISO_CURRENCY"		"AMERICA"
"NLS_NUMERIC_CHARACTERS"	".,"
"NLS_CHARACTERSET"		"WE8ISO8859P1"
"NLS_CALENDAR"			"GREGORIAN"
"NLS_DATE_FORMAT"		"DD-MON-RR"
"NLS_DATE_LANGUAGE"		"AMERICAN"
"NLS_SORT"			"BINARY"
"NLS_TIME_FORMAT"		"HH.MI.SSXFF AM"
"NLS_TIMESTAMP_FORMAT"		"DD-MON-RR HH.MI.SSXFF AM"
"NLS_TIME_TZ_FORMAT"		"HH.MI.SSXFF AM TZR"
"NLS_TIMESTAMP_TZ_FORMAT"	"DD-MON-RR HH.MI.SSXFF AM TZR"
"NLS_DUAL_CURRENCY"		"$"
"NLS_COMP"			"BINARY"
"NLS_LENGTH_SEMANTICS"		"BYTE"
"NLS_NCHAR_CONV_EXCP"		"FALSE"
"NLS_NCHAR_CHARACTERSET"	"AL16UTF16"
"NLS_RDBMS_VERSION"		"10.2.0.1.0"

[fxp]

Looks to be related to Oracle configuration