Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Oracle error creating tables for web security

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Oracle error creating tables for web security

    Hello everybody,

    While I am trying to activate web security in SQL mode, and during the creation of the 4 security tables, I received errors as below:

    - I tested with Oracle 9i (9.2) and the error was: ORA-01461: can bind a LONG value only for insert into a LONG column
    - I tested with Oracle 11 and the error was: ORA-0094 "guid": invalid identifier

    Since web security is pretty straight forward, I am wondering what's the problem.

    I appreciate Alpha's developers any help.

    Best Regards
    Vangelis

  • #2
    Re: Oracle error creating tables for web security

    here is the table structures I use

    -- Start of DDL Script for Table BROKERSUITEADMIN.WEBSEC_EXPIRED_T
    -- Generated 23-May-2014 16:21:08 from [email protected]

    -- Drop the old instance of WEBSEC_EXPIRED_T
    DROP TABLE websec_expired_t
    /

    CREATE TABLE websec_expired_t
    (user_guid VARCHAR2(36 BYTE) NOT NULL,
    password VARCHAR2(60 BYTE),
    lastused DATE)
    SEGMENT CREATION IMMEDIATE
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    TABLESPACE data128k
    STORAGE (
    INITIAL 65536
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    NOCACHE
    MONITORING
    NOPARALLEL
    LOGGING
    /





    -- Constraints for WEBSEC_EXPIRED_T

    ALTER TABLE websec_expired_t
    ADD CONSTRAINT wse_pk PRIMARY KEY (user_guid)
    USING INDEX
    PCTFREE 10
    INITRANS 2
    MAXTRANS 255
    TABLESPACE indx32k
    STORAGE (
    INITIAL 163840
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    /


    -- Comments for WEBSEC_EXPIRED_T

    COMMENT ON TABLE websec_expired_t IS 'Short Name : WSU'
    /

    -- End of DDL Script for Table BROKERSUITEADMIN.WEBSEC_EXPIRED_T

    -- Start of DDL Script for Table BROKERSUITEADMIN.WEBSEC_GROUPS_T
    -- Generated 23-May-2014 16:21:09 from [email protected]

    -- Drop the old instance of WEBSEC_GROUPS_T
    DROP TABLE websec_groups_t
    /

    CREATE TABLE websec_groups_t
    (group_guid VARCHAR2(36 BYTE) NOT NULL,
    group_name VARCHAR2(60 BYTE),
    updweb DATE,
    updlocal DATE)
    SEGMENT CREATION IMMEDIATE
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    TABLESPACE data128k
    STORAGE (
    INITIAL 65536
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    NOCACHE
    MONITORING
    NOPARALLEL
    LOGGING
    /





    -- Constraints for WEBSEC_GROUPS_T

    ALTER TABLE websec_groups_t
    ADD CONSTRAINT wsg_pk PRIMARY KEY (group_guid)
    USING INDEX
    PCTFREE 10
    INITRANS 2
    MAXTRANS 255
    TABLESPACE indx32k
    STORAGE (
    INITIAL 163840
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    /


    -- Comments for WEBSEC_GROUPS_T

    COMMENT ON TABLE websec_groups_t IS 'Short Name : WSG'
    /

    -- End of DDL Script for Table BROKERSUITEADMIN.WEBSEC_GROUPS_T

    -- Start of DDL Script for Table BROKERSUITEADMIN.WEBSEC_MEMBERS_T
    -- Generated 23-May-2014 16:21:09 from [email protected]

    -- Drop the old instance of WEBSEC_MEMBERS_T
    DROP TABLE websec_members_t
    /

    CREATE TABLE websec_members_t
    (group_guid VARCHAR2(36 BYTE) NOT NULL,
    user_guid VARCHAR2(36 BYTE) NOT NULL,
    updweb DATE,
    updlocal DATE)
    SEGMENT CREATION IMMEDIATE
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    TABLESPACE data128k
    STORAGE (
    INITIAL 65536
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    NOCACHE
    MONITORING
    NOPARALLEL
    LOGGING
    /





    -- Constraints for WEBSEC_MEMBERS_T

    ALTER TABLE websec_members_t
    ADD CONSTRAINT wsm_pk PRIMARY KEY (user_guid, group_guid)
    USING INDEX
    PCTFREE 10
    INITRANS 2
    MAXTRANS 255
    TABLESPACE indx32k
    STORAGE (
    INITIAL 163840
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    /


    -- Comments for WEBSEC_MEMBERS_T

    COMMENT ON TABLE websec_members_t IS 'Short name : WSM'
    /

    -- End of DDL Script for Table BROKERSUITEADMIN.WEBSEC_MEMBERS_T

    -- Start of DDL Script for Table BROKERSUITEADMIN.WEBSEC_USERS_T
    -- Generated 23-May-2014 16:21:10 from [email protected]

    -- Drop the old instance of WEBSEC_USERS_T
    DROP TABLE websec_users_t
    /

    CREATE TABLE websec_users_t
    (guid VARCHAR2(36 BYTE) NOT NULL,
    userid VARCHAR2(250 BYTE),
    password VARCHAR2(60 BYTE),
    rememberme NUMBER(*,0),
    redirpage VARCHAR2(60 BYTE),
    passent DATE,
    passexp DATE,
    email VARCHAR2(250 BYTE),
    secques VARCHAR2(100 BYTE),
    secans VARCHAR2(60 BYTE),
    updweb DATE,
    updlocal DATE,
    ulink VARCHAR2(40 BYTE))
    SEGMENT CREATION IMMEDIATE
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    TABLESPACE data128k
    STORAGE (
    INITIAL 65536
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    NOCACHE
    MONITORING
    NOPARALLEL
    LOGGING
    /





    -- Constraints for WEBSEC_USERS_T

    ALTER TABLE websec_users_t
    ADD CONSTRAINT wsu_pk PRIMARY KEY (guid)
    USING INDEX
    PCTFREE 10
    INITRANS 2
    MAXTRANS 255
    TABLESPACE indx32k
    STORAGE (
    INITIAL 163840
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    )
    /


    -- Comments for WEBSEC_USERS_T

    COMMENT ON TABLE websec_users_t IS 'Short name : WSU'
    /

    -- End of DDL Script for Table BROKERSUITEADMIN.WEBSEC_USERS_T

    bear in mind the tablespaes will need to be changed to fit your database

    cheers
    Garth


    Originally posted by vagkomninos View Post
    Hello everybody,

    While I am trying to activate web security in SQL mode, and during the creation of the 4 security tables, I received errors as below:

    - I tested with Oracle 9i (9.2) and the error was: ORA-01461: can bind a LONG value only for insert into a LONG column
    - I tested with Oracle 11 and the error was: ORA-0094 "guid": invalid identifier

    Since web security is pretty straight forward, I am wondering what's the problem.

    I appreciate Alpha's developers any help.

    Best Regards
    Vangelis

    Comment


    • #3
      Re: Oracle error creating tables for web security

      Hi Garth

      Thank you for your detailed reply. I will give it a try.

      Thanks again
      Regards

      Comment

      Working...
      X