[JRASERVER-8293] Import fails if searchrequest:request data too large

Type: Bug
Resolution: Fixed
Priority: Low (View bug fix roadmap)
Fix Version/s: 4.0 Iteration 36, 4.0 Milestone 6, 4.0
Affects Version/s: 3.3.2
Component/s: Migration - Server to Cloud
Labels:
- affects-server
- engine_room
Environment:

Orion 2.0.2, Oracle 91 w/ 10g thin driver

Introduced in Version:
3.03
Support reference count:
4
Bug Fix Policy:
View Atlassian Server bug fix policy

Entity "SearchRequest" has field "request" of type "very-long"
Needs to be "extremely-long" for import into Oracle as standalone instance seemed to allow longer content length than 4000 characters. (that whole clob thing)

Throws:
ORA-01461: can bind a LONG value only for insert into a LONG column

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

searchrequest.txt
4 kB
21/Oct/2005 2:38 PM

is duplicated by

JRASERVER-14085 SearchRequest entity should use a extemely-long field types on Oracle 10g

Closed

is related to

JRASERVER-14544 The username in filtersubscription table is too short and does not match userbase

Closed

JRASERVER-14701 OSPropertyText table should have the value column set to extremely-long datatype

Closed

relates to

JRASERVER-13329 Error when adding a group with name longer than 60 characters to a notification scheme: too long for database column

Gathering Impact

Assignee:: Mark Lassau (Inactive)

Reporter:: Eric White

Affected customers:: 0 This affects my team

Watchers:: 2 Start watching this issue

Created:: 20/Oct/2005 5:27 PM

Updated:: 27/Mar/2019 11:49 PM

Resolved:: 29/May/2009 6:26 AM

Jira Data Center

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates